Geolocation compliance for a mobile workforce

ABSTRACT

A system and method that uses geo-location and a rules engine to facilitate compliance to federal, state, and local regulations as well as company policies across different jurisdictions that may have different compliance regulations. A mobile workforce may use the techniques herein to manage work assignments, report activities, and to manage and track time. This technology may be used, e.g., in the transportation industry, but is not limited to this industry.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/189,252, filed Nov. 13, 2018, which is a divisional of U.S.application Ser. No. 15/353,049, filed Nov. 16, 2016, which claims thebenefit of and priority to U.S. Provisional Application No. 62/256,355,filed Nov. 17, 2015, and to U.S. Provisional Application No. 62/421,507,filed Nov. 14, 2016, all of which are incorporated by reference hereinin their entireties.

BACKGROUND OF THE DISCLOSURE 1.0 Field of the Disclosure

The present disclosure relates to a method, a system and a computerprogram for geo-based regulation and compliance and more particularly,to a system, method and computer program for geo-based regulation andcompliance for mobile workforce, among other features.

2.0 Related Art

The nature of many jobs in today's modern economy is such that personnelroutinely perform work activities in various cities, municipalities,counties, and states and cross between different jurisdictions duringthe same workday. For example, commercial operators, e.g., professionaldrivers, often cross state lines perhaps many times during a givenworkday and drive in and out of different cities and counties as they goabout their work. Recently there has been a dramatic increase in newregulations and enforcement activity designed to control details ofemployment relationships.

For example, cities and states may have different rules with respect torequired meal breaks, required rest breaks, sick leave entitlements, aswell as unique minimum wage levels. Companies are lacking auser-friendly technological solution to track and monitor where and forhow long personnel perform work activity and to capture data to ensurepersonnel are taking required meal and rest breaks. Such a solution,which does not currently exist, would enhance a company's ability toconduct efficient and compliant nationwide operations despite thegrowing patchwork of unique state and local regulations.

SUMMARY OF THE DISCLOSURE

In one aspect, the present disclosure provides a method, a system and acomputer program for geo-based regulation and compliance for mobileworkforce.

In one aspect, a system for geo-based regulation and compliance formobile workforce is provided comprising a server comprising a computerconfigured to receive GPS location information related to a plurality ofmobile units, a rules compliance module executable by a computer andconfigured to determine rules for a jurisdiction based on a geographiclocation of the plurality of mobile units, a rest break optimizer moduleexecutable by the server and configured to determine at least one restbreak plan based on the geographic location of at least one of theplurality of mobile units, and configured to determine a labor lawcompliance plan based on the geographic location of at least one of theplurality of mobile units and a display device located in or associatedwith the at least one of the plurality of mobile units for receiving adirective to conform to the at least one rest break plan. The at leastone of the plurality of mobile units may be configured to provide to theserver in response to the directive at least one of: an opt-out of breakactivity, a defer break activity, a take a break activity. The systemfurther comprising a rules engine configured to de-conflict rules formultiple jurisdictions related to a plurality of different geographiclocations traversed by the at least one of the plurality of mobileunits. The rest break optimizer module may be configured to determine atleast one rest break plan based on different geographic locations of atleast one of the plurality of mobile units, and may be configured todetermine a compliance plan based on different geographic locations ofat least one of the plurality of mobile units for sequencing rest breaksto maximize work break synergy, wherein the different geographiclocations include jurisdictions having differing labor laws affectingthe at least one rest break plan.

In one aspect, a computer-implemented method for geo-based regulationand compliance for mobile workforce comprises providing a serverconfigured to receive GPS location information related to a plurality ofmobile units, providing a rules compliance module executable by acomputer and configured to determine rules for a jurisdiction based on ageographic location of the plurality of mobile units, providing a restbreak optimizer module executable by the computer and configured todetermine at least one rest break plan based on the geographic locationof at least one of the plurality of mobile units, and configured todetermine a compliance plan based on the geographic location of at leastone of the plurality of mobile units. The method may further includethat the plurality of mobile units are configured to receive and displayfrom the computer a directive indicating a activity to conform to the atleast one rest break plan.

In one aspect, a computer program product embodied on a non-transitorystorage medium that, when read and executed by a computer, performs thesteps for geo-based regulation and compliance for mobile workforceaccording to the computer-implemented method described above.

In one aspect, a system for geo-based regulation and compliance formobile workforce comprises a server comprising a computer configured toreceive GPS location information related to a plurality of mobile unitsand a rules engine module executable by a computer and configured todetermine rules for a jurisdiction based on a geographic location of theplurality of mobile units, and a display device located in or associatedwith the at least one of the plurality of mobile units for receiving adirective to conform to at least one rest break plan.

In one aspect, a system is provided for dynamic geographic based rulesmanagement to identify and de-conflict a plurality of rules that areapplicable to: i) a role of a user, ii) at least one region, and iii) atleast one timeframe based on a previous geographic location of themobile a current location of the user, at least one planned futurelocation of the user, or any combination thereof, the system comprising:a rules engine module executing on a mobile device associated with theuser; a global positioning system (GPS) device to track a plurality oflocations of the mobile device; wherein the rules engine module sendsgeographic locations over a network to a remote geographic informationservice (GIS) and receives at least one region for identifying andde-conflicting the plurality of rules. The plurality of rules may bedynamically identified and comprises one or more of: predefined rules,removable rules and updateable rules. The region may comprise ajurisdiction or a geographic area. The jurisdiction may comprise acountry, a county, a city, a state, a postal code area, or a predefinedarea. The geographic area may be defined by an organization thatspecifies which of the plurality of rules are to be applied to thegeographic area. The rules engine module may manage the plurality ofrules that align to workday requirements, work breaks, personnel pay, ortax rules. The at least one region may be a plurality of regions and therule engine module identifies and de-conflicts the plurality of rulesthat are applicable to the plurality of regions. The system may furthercomprise a repository of the plurality of rules maintained by a server,the plurality of rules reflect laws, policy or regulations for the atleast one region. The plurality of rules may reflect at least one of:organizational rules and policies for the at least one region, a taxregulation and a pay regulation. The rules engine module may dynamicallyidentify for a predetermined duration at least one of the plurality ofrules for which the user must abide based on the role of the user andthe at least one future planned location. The mobile device may beassociated with a vehicle.

In one aspect, a system is provided for dynamically capturing andtracking activities related to an individual; comprising: a mobiledevice associated with the individual; a global positioning system (GPS)device for providing GPS location information of the mobile device; anda server to receive from a computer associated with the mobile deviceover a wireless communication link a plurality of activities related tothe individual, each of the plurality of activities including timeduration information and the GPS location information of the mobiledevice for recording the plurality of activities, wherein the mobiledevice determines compliance to a set of dynamic rules and generates anotice when not in compliance to initiate renewed compliance. The set ofdynamic rules may define activities that require completion by theindividual over time to satisfy at least one rule and wherein each ofthe received plurality of activities is used to determine compliancewith the at least one dynamic rule. The set of dynamic rules may defineactivities that require completion by the individual to satisfy aplurality of the set of rules and wherein each of the received pluralityof activities is used to determine compliance with the set of dynamicrules. The set of dynamic rules are applicable to the plurality ofjurisdictions and reflect laws or regulations for the plurality ofjurisdictions. Activities may be created to capture tasks associatedwith the set of rules, compensable work, or billable work. The mobileunit may comprises a vehicle. The vehicle may be configured to provideevent data to the mobile device, the event data including at least oneof: a current speed, an odometer reading and a power-take-off state. Themobile device may use the event data to generate an activity for use indetermining compliance to the set of dynamic rules. The server may beconfigured to send new activity types to the mobile unit, the newactivity types for satisfying existing rules, new rules or for recordingbillable or compensable work. The server may be configured to send newevent types to the mobile unit, the new event types for creating newtypes of activities.

In one aspect, a computer-implemented method is provided for dynamicallycapturing and tracking activities related to an individual, comprising:receiving a plurality of activities related to an individual, each ofthe plurality of activities including time duration information and GPSlocation information of a mobile unit associated with the individual;determining compliance or non-compliance to the plurality of rules basedon the received plurality of activities, the plurality of rulesapplicable to the plurality of regions and reflect laws or regulationsfor the plurality of regions; and providing a warning notification tothe mobile unit before non-compliance occurs or sending a non-compliancenotification when non-compliance occurs. The step of determiningcompliance may include determining activities that require completion bythe individual over time to satisfy at least one of the plurality ofrules and wherein each of the received plurality of activities is usedto determine compliance with the at least one of the plurality of rules.The computer-implemented method may further comprise sending anon-compliance notification to a third-party when non-compliance isdetermined. The mobile unit may comprise a vehicle. Thecomputer-implemented method may further comprise receiving event data ata mobile device, the event data including at least one of: a currentspeed, an odometer reading and a power-take-off state. Thecomputer-implemented method may further comprise generating an activitybased on the received event data for use in determining compliance tothe plurality of rules. The computer-implemented method may furthercomprise sending by the server new activity types to the mobile unit,the new activity types for satisfying existing rules or new rules. Thecomputer-implemented method may further comprise sending by the servernew event types to the mobile unit, the new event types for creating newtypes of activities.

In one aspect, a system is provided to optimize a plan of activities fora workday and to monitor the plan for compliance, comprising: anoptimizer module executing on a computer that receives work tasks to beperformed by an individual for a work period; an interface to ageographic information system (GIS) tool, the GIS tool configured toprovide to the optimizer module a route based on projected destinationsrelated to the work tasks, wherein the optimizer module creates anoptimized work plan for the individual including an optimized break planbased on the received work tasks and the route; and a compliance moduleexecuting on a computer that receives geographic location informationfrom a GPS device indicative of at least one location of the individualover a time period, the compliance module monitoring compliance to theoptimized work plan including the optimized break plan and creating analert when not in compliance. The compliance module may monitorcompliance to the work plan based on received event data related to avehicle associated with the individual. The individual may be a vehicleoperator and the work plan may be presented to a mobile unit for viewingby the individual on a display thereby creating a cohesive experience tothe individual which is the work plan that includes the route, the worktasks, workday expectations, the optimized break plan, monitoring andsequencing thereof. The compliance module may monitor the work planthroughout a workday, and includes receiving an event and translatingthe event to an activity to satisfy at least one rule associated withthe work plan. The optimizer module may create an optimized break planto identify and de-conflict at least one rule based on a startinglocation, an ending location and zero or more intermediary locations.The at least one rule may reflect a law, a company policy or aregulation for at least one region. The system may further comprising arules engine module executing on the computer that identifies at leastone rule requiring compliance by the individual for the optimized workplan. The at least one rule may be a plurality of rules that reflect aplurality of regions with differing labor regulations. The optimizermodule resolves at least one conflict in labor regulations between atleast two of the plurality of regions.

In one aspect, a computer-implemented method to optimize a plan ofactivities for a workday and to monitor the plan for compliance,comprising: receiving at a computer work tasks to be performed by anindividual for a work period; determining at the at least one computer aroute using a geographic information system (GIS) tool based on one ormore geographic locations related to the work tasks, optimizing at thecomputer a work plan for the individual including an optimized breakplan based on the received work tasks, and based on at least one rulerelated to a region and the determined route; receiving at the computergeographic location information from a GPS device indicative of at leastone location of the individual over a time period; monitoring at thecomputer compliance of the individual to the work plan; and creating analert when there is a non-compliance. The computer may comprises acomputer at a vehicle associated with the individual. The one or moregeographic locations may comprise a plurality of geographic locations tobe traversed by the individual over the course of a workday and includesa plurality of: a starting location, an intermediate location and anending location. The step for monitoring may monitor compliance to thework plan based on a received event related to a vehicle associated withthe individual. The individual may be a vehicle operator, thecomputer-implemented method further comprising displaying the work planon a display for viewing by the individual thereby creating a cohesiveexperience to the individual which is the work plan that includes theroute, the work tasks, workday expectations, the optimized break plan,monitoring and sequencing thereof. The step for monitoring may includemonitoring the work plan throughout a workday, and may include receivingan event and translating the event to an activity to satisfy the atleast one rule associated with the work plan. The step for optimizingmay create the optimized break plan to identify and de-conflict at leastone rule based on a starting location, an ending location and zero ormore intermediary locations. The at least one rule may reflect a companypolicy, a law for at least one region or a regulation for the at leastone region. The computer-implemented method may further compriseidentifying the at least one rule requiring compliance by the individualfor the optimized work plan. The at least one rule may a plurality ofrules that reflect a plurality of regions with differing laborregulations. The computer-implemented method may further comprisingresolving at least one conflict in regulations between at least two ofthe plurality of regions. The computer-implemented method may furthercomprising modifying the work plan at a mobile unit associated with theindividual to account for unexpected changes to the workday. Thecomputer-implemented method may further comprising creating a list ofrequired breaks based on the received work tasks and the step foroptimizing optimizes the work plan to minimize time related to the routeand the required breaks. The step of creating an alert may send amessage to the individual, a third-party, or both. The step formonitoring determines there is an imminent non-compliance to the atleast one rule, further comprising sending a notice to the individual ata vehicle before there is an actual non-compliance. Thecomputer-implemented method may further comprising capturing one or moreactivities related to the individual to record compliance to the atleast one rule or the work plan. The at least one rule may relate to atax regulation or a pay regulation. The region may comprise ajurisdiction or a geographic area. The jurisdiction may comprise acountry, a county, a city, a state, a postal code area, or a predefinedarea. The geographic area may be defined by an organization thatspecifies which of the plurality of rules are to be applied to thegeographic area.

Additional features, advantages, and embodiments of the disclosure maybe set forth or apparent from consideration of the detailed descriptionand drawings. Moreover, it is to be understood that both the foregoingsummary of the disclosure and the following detailed description areexemplary and intended to provide further explanation without limitingthe scope of the disclosure as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure, are incorporated in and constitute apart of this specification, illustrate embodiments of the disclosure,and together with the detailed description, serve to explain theprinciples of the disclosure. No attempt is made to show structuraldetails of the disclosure in more detail than may be necessary for afundamental understanding of the disclosure and the various ways inwhich it may be practiced. In the drawings:

FIG. 1 is an illustrative block diagram of an example system forgeo-based regulation and compliance for mobile workforce, configuredaccording to principles of the disclosure.

FIG. 2 is a block diagram of various example client deviceconfigurations that may be employed to provide end user functionalitywhile interacting with a server, configured according to principles ofthe disclosure.

FIG. 3 is an example overview functional block diagram of a systemincluding components for geo-based regulation and compliance for mobileworkforce showing an example functional interrelationship of thosecomponents, configured according to principles of the disclosure.

FIG. 4A is an example flow diagram of an process to update Rules forPeriod, performed according to principles of the disclosure.

FIG. 4B is a flow diagram showing an example process to determine if anew rule is satisfied by an activity that has been previously recorded,the process performed according to principles of the disclosure.

FIG. 5 is a flow chart of an example process for optimization of anindividual's workday and breaks, the process performed according toprinciples of the disclosure.

FIG. 6A is a flow diagram showing an example process to determine rulesto be monitored for compliance, the process performed according toprinciples of the disclosure.

FIG. 6B is a flow diagram showing an example process for rule compliancemonitoring and notification, the process performed according toprinciples of the disclosure.

FIG. 7 is an example interface to describe an activity configuratorfunctionality, configured according to principles of the disclosure.

FIG. 8A is an illustration showing an example of functions provided inthe activity logger application program interface (API) and how theyinteract with each other. The ovals are included to provide examplecontext on how these functions would be used, according to principles ofthe disclosure.

FIG. 8B is a flow diagram showing an example process for a createactivity function, performed according to principles of the disclosure.

FIG. 8C is a flow diagram showing an example process for a startactivity function, performed according to principles of the disclosure.

FIG. 8D is a flow diagram showing an example process for an end activityfunction, performed according to principles of the disclosure.

FIG. 8E is a flow diagram showing an example process for a searchactivity function, performed according to principles of the disclosure.

FIG. 8F is a flow diagram showing an example process for an updateactivity function, performed according to principles of the disclosure.

FIG. 8G is a flow diagram showing an example process for a deleteactivity function, performed according to principles of the disclosure.

FIG. 8H is a flow diagram showing an example process for set rules tosatisfied function, performed according to principles of the disclosure.

FIG. 8I is a flow diagram showing an example process for removesatisfied function, performed according to principles of the disclosure.

FIG. 8J is a flow diagram showing an example to manage approvalnotification process, performed according to principles of thedisclosure.

FIG. 8K is a flow diagram showing an example process to receive newexternal events using a get event function, performed according toprinciples of the disclosure.

FIG. 8L is a flow diagram showing an example process for approveactivity function performed according to principles of the disclosure.

FIG. 8M is a flow diagram showing an example process for disapproveactivity function performed according to principles of the disclosure.

FIG. 8N is a flow diagram showing an example process to createconsistent location calculations based on a GPS reading, performedaccording to principles of the disclosure.

FIG. 8O is a flow diagram showing an example process to interact with aGIS service for a get geocode function, performed according toprinciples of the disclosure.

FIG. 9 is a functional block diagram of an event API 232 including a setof methods to permit an external system to interact with an activityengine of server, configured according to principles of the disclosure.

The present disclosure is further described in the detailed descriptionthat follows.

DETAILED DESCRIPTION OF THE DISCLOSURE

The disclosure and the various features and advantageous details thereofare explained more fully with reference to the non-limiting embodimentsand examples that are described and/or illustrated in the accompanyingdrawings and detailed in the following description. It should be notedthat the features illustrated in the drawings are not necessarily drawnto scale, and features of one embodiment may be employed with otherembodiments as the skilled artisan would recognize, even if notexplicitly stated herein. Descriptions of well-known components andprocessing techniques may be omitted so as to not unnecessarily obscurethe embodiments of the disclosure. The examples used herein are intendedmerely to facilitate an understanding of ways in which the disclosuremay be practiced and to further enable those of skill in the art topractice the embodiments of the disclosure. Accordingly, the examplesand embodiments herein should not be construed as limiting the scope ofthe disclosure. Moreover, it is noted that like reference numeralsrepresent similar parts throughout the several views of the drawings.

A “computer”, also referred to as a “computing device” or a “CPU,” asused in this disclosure, means any machine, device, circuit, component,or module, or any system of machines, devices, circuits, components,modules, or the like, which are capable of manipulating data accordingto one or more instructions, such as, for example, without limitation, aprocessor, a microprocessor, a central processing unit, a generalpurpose computer, a super computer, a personal computer, a laptopcomputer, a palmtop computer, a notebook computer, a desktop computer, aworkstation computer, a server, or the like, or an array of processors,microprocessors, central processing units, general purpose computers,super computers, personal computers, laptop computers, palmtopcomputers, cell phone, notebook computers, desktop computers,workstation computers, servers, or the like. Further, the computer mayinclude an electronic device configured to communicate over acommunication link. The electronic device may include, for example, butis not limited to, a mobile telephone, a personal data assistant (PDA),a mobile computer, a laptop, a tablet, a stationary computer, a smartphone, mobile station, user equipment, or the like.

A “server”, as used in this disclosure, means any combination ofsoftware and/or hardware, including at least one application and/or atleast one computer to perform services for connected clients. The atleast one server application may include, but is not limited to, forexample, an application program that can accept connections to servicerequests from clients by sending back responses to the clients. Theserver may be configured to run the at least one application, oftenunder heavy workloads, unattended, for extended periods of time withminimal human direction. The server may include a plurality of computersconfigured, with the at least one application being divided among thecomputers depending upon the workload. For example, under light loading,the at least one application can run on a single computer. However,under heavy loading, multiple computers may be required to run the atleast one application. The server, or any if its computers, may also beused as a workstation.

A “database”, as used in this disclosure, means any combination ofsoftware and/or hardware, including at least one application and/or atleast one computer. The database may include a structured collection ofrecords or data such as a table, or organized according to a databasemodel, such as, for example, but not limited to at least one of arelational model, a hierarchical model, a network model or the like. Thedatabase may include a database management system application (DBMS) asis known in the art. The at least one application may include, but isnot limited to, for example, an application program that can acceptconnections to service requests from clients by sending back responsesto the clients. The database may be configured to run the at least oneapplication, often under heavy workloads, unattended, for extendedperiods of time with minimal human direction.

A “network,” as used in this disclosure, means an arrangement of two ormore communication links. A network may include, for example, a publicnetwork, a cellular network, the Internet, a local area network (LAN), awide area network (WAN), a metropolitan area network (MAN), a personalarea network (PAN), a campus area network, a corporate area network, aglobal area network (GAN), a broadband area network (BAN), anycombination of the foregoing, or the like. The network may be configuredto communicate data via a wireless and/or a wired communication medium.The network may include any one or more of the following topologies,including, for example, a point-to-point topology, a bus topology, alinear bus topology, a distributed bus topology, a star topology, anextended star topology, a distributed star topology, a ring topology, amesh topology, a tree topology, or the like.

A “communication link”, as used in this disclosure, means a wired and/orwireless medium that conveys data or information between at least twopoints. The wired or wireless medium may include, for example, ametallic conductor link, a radio frequency (RF) communication link, anInfrared (IR) communication link, an optical communication link, or thelike, without limitation. The RF communication link may include, forexample, WiFi, WiMAX, IEEE 802.11, DECT, 0G, 1G, 2G, 3G or 4G cellularstandards, Bluetooth, ZigBee or the like.

The terms “including”, “comprising” and variations thereof, as used inthis disclosure, mean “including, but not limited to”, unless expresslyspecified otherwise.

The terms “a”, “an”, and “the”, as used in this disclosure, means “oneor more”, unless expressly specified otherwise. A “pre-determined timeperiod” and may be a period of time such as, e.g., a day, a week, month,year, one hour or several hours.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

Although process steps, method steps, algorithms, functions or the like,may be described in a sequential order, such processes, methods,algorithms and functions may be configured to work in alternate orders.In other words, any sequence or order of steps that may be describeddoes not necessarily indicate a requirement that the steps be performedin that order. The steps of the processes, methods or algorithmsdescribed herein may be performed in any order practical. Further, somesteps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device or article may be used in place of asingle device or article. Similarly, where more than one device orarticle is described herein, it will be readily apparent that a singledevice or article may be used in place of the more than one device orarticle. The functionality or the features of a device may bealternatively embodied by one or more other devices which are notexplicitly described as having such functionality or features.

A “computer-readable medium”, as used in this disclosure, means anymedium that participates in providing data (for example, instructions)which may be read by a computer. Such a medium may take many forms,including non-volatile media, volatile media, and transmission media.Non-volatile media may include, for example, optical or magnetic disksand other persistent memory. Volatile media may include dynamic randomaccess memory (DRAM). Transmission media may include coaxial cables,copper wire and fiber optics, including the wires that comprise a systembus coupled to the processor. Common forms of computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other non-transitory storage mediumfrom which a computer can read.

Various forms of computer readable media may be involved in carryingsequences of instructions to a computer. For example, sequences ofinstruction (i) may be delivered from a RAM to a processor, (ii) may becarried over a wireless transmission medium, and/or (iii) may beformatted according to numerous formats, standards or protocols,including, for example, WiFi, WiMAX, IEEE 802.11, DECT, 0G, 1G, 2G, 3G,4G or 5G cellular standards, Bluetooth, ZigBee or the like. Computerreadable media may be non-transitory computer readable media.

The nature of many jobs in the modem economy often requires personnel toroutinely perform activities in various cities, municipalities,countries, and states and cross between such different jurisdictionsduring the same work day or predetermined time period. For example,commercial operators often cross state lines many times during a givenworkday and drive in and out of different cities and counties as they goabout their work. There has been an increase in new ordinances and statelaws, including an increase in enforcement activity for controllingemployment relationships. For example, cities and states have differentrules with respect to required meal breaks, required rest breaks, sickleave and entitlements, as well as differing minimum wage levels.Companies often do not have a technological solution to accurately trackand monitor where and for how long personnel perform work activities andfor capturing data to ensure regulation compliance, such as across anationwide setting.

In one aspect, this present disclosure describes a system and methodthat uses geo-location and a rules engine to facilitate compliance tofederal, state, and local regulations as well as company policies.Moreover, the system and methods according to principles of thisdisclosure may be used by a mobile workforce to manage work assignments,report activities, and to manage and track time as related to determinedgeographic locations, such as by global positioning system (GPS). Thissystem and method according to principles of this disclosure may beused, e.g., in the transportation industry, but is not limited to thisindustry.

FIG. 1 is an illustrative block diagram of an example system forgeo-based regulation and compliance for mobile workforce, configuredaccording to principles of the disclosure. The system 100 may includeone or more mobile units 105 a-105 c, which may include but is notlimited to a vehicle 112 a-112 c, a computing device 110 a-110 c,communications unit 111 a-111 c, user interface 114 a-114 c, and a byglobal positioning system (GPS) 113 a-113 c. These may be contained inone device or multiple units connected though a common local areanetwork (LAN).

The one or more mobile units 105 a-105 c may be equipped with acomputing device 110 a-110 c to control and interface with acommunications unit 111 a-111 c for communicating across a network 125(which may be, e.g., a cellular network) via a communication link 130 toa server 115. The communication link 130 may be bi-directional. Thecomputing device 110 a-110 c may also interface with a vehicle e.g.,such as a truck, bus, or similar vehicle 112 a-112 c for the purpose ofreceiving events and providing context of the user based on vehicleoperation.

The computing device 110 a-110 c may also interact with a user interface114 a-114 c including an input device to receive input from a user andan output to convey messages and output to a user (e.g., a driver) ofthe one or more mobile units 105 a-105 c. The input device 114 a-114 cmay comprise of but not limited to a touch sensitive screen, a keypad, akeyboard, a mouse, voice activated input device. The output device mayinclude but not limited to a visual screen, LED or warning lights,dashboard indicators, sound such as voice or tones. The computing device110 a-110 c may also interface with a GPS tracking device 113 a-113 cthat may be configured to provide location data information of the oneor more mobile units 105 a-105 c.

A system user such as a system manager may interact with the server 115via an input device 116, such as to implement or manage the rules amongother functions, as described more fully below. In some configurations,the input device 116 may be connected to the server 115 over the network125.

As the one or more mobile units 105 a-105 c travels from one geographiclocation to another geographic location, the GPS tracking device 113a-113 c may provide updates of the current location to the computingdevice 110 a-110 c, which in turn, may provide updates to the server115. The updates may be continuous or may be periodic.

The system 100, in particular the server 115, may record in the database120 activities of the one or more mobile units 105 a-105 c and also theassociated user (as part of normal business processes) and may tag suchactivities with geo-locations provided by the GPS tracking device 113a-113 c.

A Rule herein is a representation of government laws, regulations orcompany rules and policies that an individual is expected to showcompliance to. In the applications herein a rule includes an expectationof an activity that needs to be performed. Rules are tied to thespecific geographic regions or jurisdictions, and user roles that thelaw, regulations, rules or policies apply to. For example, to manage USHours of Service, rules to represent Federal Motor Carrier SafetyAdministration (FMCSA) standards (Title 49 Part 395—Hours of Service ofDrivers) may be created and tied to the US region with a role of drive.Likewise, to manage Canadian Hours of Service, rules to representCanadian Council of Motor Transport Administrators (CCMTA) CommercialVehicle Drivers Hours of Service Regulations may be created and tied toCanadian region with a role of driver. A third set of rules may becreated that aligns to the Oil & Gas Related Exceptions in the FederalHours-of-Service Rules and may be tied to a U.S. region with a role ofOilfield Driver. To ensure alignment to California labor laws, theapplication may include rules to manage California's Meal and Rest breaklaws which would be tied to California Region and all roles.

In one aspect, the computing device 110 a-110 c may interpret predefinedrules based on work location (as provided by the GPS tracking device 113a-113 c associated with a respective mobile unit 105 a-105 c), and may,for example, prompt a particular user associated with any one of themobile units 105 a-105 c to:

-   -   1) Enter data (e.g., via input device 114 a-114 c)    -   2) Take an action (e.g., meal or rest break) and    -   3) Record compensable and/or billable activities (e.g., hand        unload, detention, record paperwork) as a part of the user's        work process.        The server 115 may be operatively coupled 132 to a back-end        processing system (not shown) for further processing based on        information gathered and/or maintained by server 115. Such        back-end processing may include, e.g., payroll functions, human        resource functions, management functions, report generation,        billing, and the like.

FIG. 2 is a block diagram of various example configurations of MobileUnits 185, 195 and Mobile Devices 180, 190 that may be interacting witha server, configured according to principles of the disclosure. MobileUnits 185, 195 may be required to satisfy the FMCSA electronic logging(ELD) mandate as they include a connection to the vehicle 112 a-112 cusing a standard vehicle connection such as SAE J1939. SAE J1939supports real-time control functions, simple information exchanges, anddiagnostic data exchanges between electronic control units physicallydistributed throughout the vehicle 112 a-112 c. Control units mayinclude, e.g., odometer readout, power-take-off (PTO) engaged, engineRPM, speed indicator, tire pressure, engine status (On/Off), or similarinternal readout or status. Mobile Devices 180, 190 may be used as anextension of the system and method to other industries that don'trequire a connection to the vehicle.

In configuration 180, a mobile device 134 such as a tablet computer,laptop or cell phone that contain; a computing device 110 a-110 b,communication unit 111 a-111 b, global positioning unit (GPS) 113 a-113b and user interface 114 a-114 b may be used to provide end usercapability.

In Configuration 185, a mobile device 135 such as a table computer,laptop or cell phone are connected to broadband router 121 using awireless connection. The Broadband router provides connectivity to theVehicle 112 a using a standard protocol such as SAE J1708 or SAE J1939providing vehicle events to the mobile device 135. The broadband routerthen provides network connectivity 111 a-111 c to communicate to servers115. The mobile device 135 may contain; a computing device 110 a-110 b,communication unit 111 a-111 b and user interface 114 a-114 b and maycontain a global positioning unit (GPS) 113 a-113 b. The broadbandrouter may contain; a computing device 110 a-110 b, communication unit111 a-111 b and may contain a global positioning unit (GPS) 113 a-113 b.The vehicle 112 a may provide a connection to the controller areanetwork (CAN) bus to provide events to the mobile device 135.

Configuration 190, is a depiction of a generic device recognizing thatas technology advances there may be new mobile devices that contain therequired components including; a CPU 123, Storage 124, communicationunit 111 a, global positioning unit (GPS) 113 a and user interface 114 amay be used to provide end user capability.

Configuration 195, is a depiction of a generic device recognizing thatas technology advances there may be new Mobile Units that contain therequired components including; a CPU 123, Storage 124, communicationunit 111 a-111 b, global positioning unit (GPS) 113 a-113 b, userinterface 114 a and vehicle 112 a-112 c may be used to provide end usercapability.

FIG. 3 is an example overview functional block diagram of a system 200including components for geo-based regulation and compliance for mobileworkforce showing an example functional interrelationship of thosecomponents, configured according to principles of the disclosure. Abrief introduction of these components follows, with a more detailedexplanation thereafter.

An event generator 230 may monitor, read, or receive events from avehicle 112 a-112 c related to statuses and states of the vehicle, aserver 115 to facilitate approval process, an application deployed oncomputing device 110 a-110 c to provide app to app communication. Eventsmay also come from a mobile device 134, 135, router 121 or from withinsystem 200 as well. The event generator 230 may log or store theseevents in an events database 225. The event generator 230 and eventsdatabase 225 typically are located within or associated with therespective mobile unit 105 a-105 c.

The activity logger application programming interface (API) 220 is atool that may be used to provide functionality to the end user at themobile unit 105 a-105 c to log their activities. The activity editor 215is a description of a generic use of the activity logger API 220. TheActivity Editor 215 may include a responsive Web Application that maypermit users to create, update and delete activities after the fact(i.e., after an activity has occurred). The activities database 235records activities as they are created or modified. The activitiesconfigurator 250 is a tool that permits a user to create, update andremove activity types in activities database 235.

The rules configurator 210 is a tool that permits a system user tocreate, update and remove rules in rules database 205. The rulesconfigurator 210 may reside and execute on server 115. The rules engine240 is a module that identifies one or more rules that a specific usermay need to follow based on inputs provided. The rules engine 240 cansatisfy what is needed by the optimizer 245 and compliance engines 250.Rules engine 240 may execute on the server 115, the computing device 110a-110 c, or both. The geographic information system (GIS) tool 280 is asystem that is designed to capture, store, manipulate, analyze, manage,and present spatial or geographical data. A GIS tool can provideinformation such as maps, geographic points, geo fences, regionmanagement, location lookup, historic route visualization, and such tothe Rules engine 240. The GIS tool 280 may execute on server 115. Theoptimizer engine 245 optimizes a user of the mobile unit 105 a-105 c,such as a truck driver, by integrating meal and rest breaks as requiredby Federal, State and local authorities for a time period, for multiplejurisdictions, based on rules. The optimizer engine 245 may execute onthe computing devices 110 a-110 c. The compliance engine 252 isconfigured to enforce rules based on geo-location of the mobile unit 105a-105 c. The compliance engine 252 may execute on the computing device110 a-110 c. In one aspect, the GPS device 113 a-113 c may report one ofmobile units 105 a-105 c physical positions. A clock 265 may provide atime stamp of GPS locations and events in the system 200 overall. Therouting tool 260 may be configured to provide, among other features, aroute given the information provided, such as, e.g., current user ofmobile unit, start location and time, stops (location and duration), endlocation, weather, traffic, fuel, cargo type and type of vehicle. Abilling tool or system 270 may receive activity information foraccounting for billable time. A pay tool or system 275 may receiveactivity information for assisting in appropriate pay calculation for amobile unit user. An activity reporting module 255 may report on variousactivities by mobile user. The regulation resource 204 may include oneor more resources for determining regulations related to variousjurisdictions such as cities, counties, states, countries. Thisresources may be a compilation of regulations from multiple sources andmay provide the guiding basis upon which rules may be created for eachof the jurisdictions for which the system 100 may provide operationalservice. The regulation resource 204 may be manually compiled,automatically compiled from jurisdiction publications and regulations,or a combination of manual and automatic.

Rule configurator 210 is a software tool executable at server 115 thatpermits a system user, such as a system administrator, to create, updateand remove rules. The rule configurator also provides an ability forsystem users to tie rules to the geographic region and user roles. Rulesmay also be assigned to a period rule (time period which the rule isvalid). Each rule can have a notification type assigned to it. Rules maybe assigned to activities and prompts via the activities configurator250. A system user may be required to login as a user to ensure properpermissions. Rule configurator 210 provides several functions including:

Rules Search

-   -   This provides an ability to explore existing Rules. The search        has an ability to find rules based on:        -   Saved Search            -   This is a drop down that contains all searches the user                has saved. Selecting one populates all of the fields                below.        -   Rules fields            -   Rule Name            -   Parent            -   Rule Type            -   Rule Family            -   Region            -   Roles            -   Active        -   Actions            -   Search                -   This takes the users input, and call queries the                    database to find all results that match.                -   Display the results in the Rules Search Results.            -   Save                -   This saves the user's search selection. When the                    user clicks save search, it may ask them to name the                    search.            -   Clear                -   This re-sets the search fields    -   Rules Search Results        -   The search results provide a list of all rules that match            the users search.        -   Data that may be displayed includes:            -   Rule Name            -   Rule Display Name            -   Rule Value            -   Rule Parent            -   Rule Type            -   Rule Family            -   Time Period            -   Overdue Notify Duration            -   Notification Type            -   Back Office Notification            -   Warning Duration            -   Warning Type            -   Active        -   Actions            -   Export                -   Export provides a delimited text file of the results                    of the search.            -   Clicking on a row                -   This opens the Rules detail page with the selected                    Rule.            -   Delete                -   This prompts a “confirm” popup. If the user                    confirms, the rule may be deleted.            -   New                -   This opens the rule detail area with none of the                    fields populated.    -   Rules Detail        -   The Rules detail area provides additional detail and            information for the user to create, update and view a rule.            If the page was called with a rule it is populated with the            data about that rule. If it was created by selecting the new            button, it may populate with no data filled in.        -   Fields            -   Rule Name                -   The rule name is the name of the rule. It is used in                    all configuration tools, and back end systems.                -   The rule name should be descriptive of the rule, and                    to benefit users, unique names make maintenance                    easiest.                -   This is a free form text field            -   Rule Display Name                -   The rule display name is what the end user sees.                    Often this rule will not be unique.                -   Rule Name, Rule Display, Name Examples (California                    Lunch Break, 30 min break), (HOS 30 min Break, 30                    min break)                -   This is a free form text field            -   Rule Value                -   This is the value that the rule applies to. The Rule                    Type determines what this value means. For example,                    if it is a “Break” Rule it will be the time in                    minutes that a break must be taken. Work Day rules                    indicate a maximum amount of time in minutes. If it                    is a pay rule, it may be a currency value.            -   Parent                -   If a rule has a parent, it supersedes the parent                    rule.                -   The user is able to select only one rule to be the                    parent.            -   Rule Type                -   Rule types is used to classify a specific high level                    grouping of rules.                -   A rule can have only one rule type.                -   Types include:                -    Work Period                -    Break                -    Pay                -    Tax            -   Rule Family                -   A rule family is a way to group rules that are part                    of the same regulation. Rule family indicates that                    specific rules cannot be satisfied by the same                    activity.            -   Region                -   Region is important, as a rule cannot exist without                    a region. A region represents a geographic area to                    which the rules apply. How the system user                    identifies and assigns the region to the tool                    depends on the GIS system used.            -   Period                -   A period represents the time period that a rule is                    valid. There can be a number of time periods. Only                    one period type can be selected.            -   Roles                -   This is a list of the end user roles to which the                    rules apply. If no roles are selected, the rule is                    valid for all roles.            -   Overdue Notify Duration                -   This indicates the time when a notification should                    be generated indicating an activity is overdue.                -   9999=do not notify                -   Number can be positive or negative. Negative                    represents minutes after rule was supposed to be                    satisfied.            -   Overdue Notification                -   Type of notification to provide to the user (Sound,                    Image, Text)                -   Value                -    if Sound or Image Type are selected, this may be a                    file path to where the sound may be on the device.                -    if it is Text, this should include the text message                    to provide to the end user.            -   Back Office Notification                -   This is a checkbox that indicates someone in the                    back office should be notified that the user is not                    in compliance.            -   Warning Duration                -   This indicates the time when we should notify that                    an activity is coming up.                -   9999=do not notify                -   Number can only be positive. Minutes before rule is                    supposed to be satisfied.            -   Warning Notification                -   Type of notification to provide to the user (Sound,                    Image, Text)                -   Value                -    if sound or image type are selected, this may be a                    file path where the sound is located on the device.                -    if it is text, this should include the text message                    to provide to the end user.            -   Active                -   Check Box that indicates whether a rule should be                    used. If Active=False, the system ignores it                    completely.        -   Actions            -   Save                -   Create or update the rule in the database.            -   Cancel

Rules Engine 240 is a tool running at the server 115, the mobile unit105 a-105 c, or both, and is configured to identify the rule or rulesthat a specific mobile unit 105 a-105 c user needs to follow based oninputs provided. To determine if a mobile unit 105 a-105 c user isrequired to satisfy a rule, three pieces of information is required: i)what role(s) the mobile unit 105 a-105 c user is performing, where theparticular mobile unit 105 a-105 c is, and the timeframe a rule needs tobe satisfied. Once a rule is identified as applying to the user, therule is added to the specific user's “Rules for Period” table (as partof the Rules database 205).

The following are example types of rules that may be configured andenforced.

-   -   a. Workday: Workday rules manage items such as the        maximum/minimum period of time for a work day, overtime rules,        FMCSA 70 hour rules & restarts. Workday rules may be tied to        break rules as more complex break rules may apply to specific        workdays.    -   b. Break: Break rules manage regulations and policies such as        mandated paid and unpaid breaks, lunch breaks and other        activities with a mandated minimum duration.    -   c. Pay: Pay rules may be used to manage items such as varying        minimum wage by region, and items such as per diem, hazard pay        or millage premium for specific geographic area.    -   d. Income, Sales and Use Taxes: These rules may be used to        support organizations or individuals who need to pay taxes        specific to a geography such as International Fuel Tax Agreement        (IFTA) Tax.

Rules may also be tied together and configured to work with each other.

-   -   a. In some cases, rules may be configured to ensure they don't        overlap        -   i. Example: 3 break rules may be required to support current            California laws that may require 2, 10-min breaks and 1,            30-min break. As a result, all 3 breaks may not be            considered satisfied when the driver takes 1, 30-min break.    -   b. In other cases, rules can be configured to allow overlap.        -   i. Example: The FMCSA 30 min break requirement if driving            for more than 8 hours can overlap with California's 30 min            meal break rule. This way when the user takes their 30 min            break both rules are satisfied.

Rules can be in a hierarchy, where a child rule may supersede the parentrule

-   -   a. Example: Minimum wage for the United States is currently        $7.25, Illinois is $8.25 and Chicago, Ill. is currently $10.50.        As Chicago is within the Illinois region (parent) it would        supersede Illinois and the United States which would be Illinois        regional parent.

Rules can be tied to a position, job or work configuration.

-   -   a. Example: Sometimes rules in the same region may be different        for specific work configuration. In the trucking industry, the        rules in the United States region are different for Farm Use,        Over the Road, Oil Field, Port Dray Short Haul.

Rules for Time Period is a significant aspect of the system 200, and maybe a first mode that other applications of system 200 may interact withthe Rules Engine 240. Rules for Period may be viewed as an instance whena rule needs to be applied, and may include the following attributes:

-   -   User ID—The user that must comply to this rule    -   Rule—The rule identification that needs to be followed    -   Satisfied—An indicator that lets system applications know if the        user completed the rule.        -   Satisfied may be checked in processes that could impact            completion such as:            -   When an activity is created            -   When an activity is changed            -   When a rule is added to rules for a period        -   Activity—The activity that was performed that caused            satisfied to be marked true.        -   Valid Period Start—is a timestamp that indicates the            earliest time an activity can start to satisfy this rule for            period.        -   Valid Period End—is the timestamp that indicates the latest            time an activity can start to satisfy the rule for the            period.            With this information, the system 200 is able to ascertain            what rules a mobile unit 105 a-105 c user needs to comply            with, at what time based on where they have been, when and            how long they were there, and the role they perform.

Update Rules for Period provides an interface for other applications ofsystem 200 may interact with the Rules Engine 240.

-   -   Inputs        -   User        -   Latitude        -   Longitude        -   Date, Time    -   Output        -   List (Rules for Period) or <null>

FIG. 4A is an example flow diagram of an Update Rules for Period processused to depict a possible way to identify new rules that apply to auser, performed according to principles of the disclosure. The flowdiagram of FIG. 4A (and all other flow diagrams herein) may alsorepresent a block diagram of components that when read from a computerreadable medium and executed by a computer perform the respective step.The optimizer engine 245 and compliance engine 252 may call this processstarting at step 400. The optimizer engine 245 may call this processwith information about points a geo position (Latitude, Longitude) andtimes in a route to have rules built that the mobile unit 105 a-105 cuser may interact with. The compliance engine 252 may call everyX-distance (predetermined distance) based on a GPS location (Latitude,Longitude) to find out if there is a new rule or rules for the currentlocation. At step 405, a determination is made to identify a definedregion(s) (e.g., state, county, locality) that the geo position fallsinto. The process may interact with a GIS system or GIS service 280 todetermine the defined regions that the point falls into. Example GISsystems may include, e.g., Nokia Here®, Google Maps®, ESRI geonet, orthe like. The GIS system 280 is typically configured to return a regionor a set of regions for the geo position. The system can use pre-definedregions such as countries, states, postal codes and cities, or it canalso use user defined regions like southwest United States.

At step 410, a check is made to determine if the mobile unit 105 a-105 cand user entered a new region. This may include determining if theregion or set of regions are the same as the region or set of regionsthe mobile unit 105 a-105 c and user were in last time Update Rules forPeriod was called. If they are in the same region, then at step 460,return <null>. However, if there is a new region, at step 415 all rulesare obtained for that region that apply to that user's role from therules database 205. All existing rules for the current period for theuser are obtained, including satisfied rules. At step 420, for each ofthe rules obtained from step 415, compare them with the existing rulesfor the period from the rules for period database 206. If at step 430,it is determined that the rule is already in rules for period 206,processing continues at step 450. However, if the rule is new, then atstep 435, a new rule is created for the period using information passedin, and the rule found to create an instance of the rule. The resultsmay include:

-   -   a. User will be the user passed in.    -   b. Rule will be the rule found in step 415.    -   c. Using the time passed in and the rules found in the rules for        period table 206 for the rule set the valid period start and        valid period end dates and time.    -   d. Satisfied may be set to False.    -   e. Activity ID may be set to null.

When a new rule is added, it may have already been satisfied by one ormore an activities. Step 440 determines if a rule has been satisfied,which may be a sub-process explained in relation to FIG. 4B below. Atstep 445, the new rule may be added to the result set in the rulesdatabase 205, and the new rule may be added to a result list 465 foreventual return at step 470. At step 450, a check may be made todetermine if there are more rules to evaluate; if so, processingcontinues at step 425. If, however, there are no more rules to evaluateas determined at step 450, then at step 455 a check may be made todetermine if any results were found. If no results were found, then anull result may be returned at step 460. If at least one result wasfound, then the result list 465 of rules may be returned at step 470.

FIG. 4B is a flow diagram showing an example process to determine if anew rule is satisfied, the process performed according to principles ofthe disclosure starting at step 480. This may be a sub-process callableas required such as at step 440 of FIG. 4A. At step 482, acquire allactivates from the activities table 235 that could satisfy the rule byquerying the activities table 235 with the following criteria: i)activity start is after the rule valid start time and date, ii) activitystart is before the rule valid end time and date, and iii) through join,the rules should be associated to this activity type.

At step 484, a check is made to determine if any activities are foundsatisfying the rule. If no activities are found, the sub-process maycomplete at step 494. If there is one or more activities foundsatisfying the rule, then at step 486, all rules with the Activity areextracted. At step 488, a check is made to determine if the new rule isthe same family as this rule. If yes, then processing continues at step492, where a check is made to determine if there are more activities. Ifthere are no more activities, the sub-process completes at step 494. Ifthere are more activities, then processing continues at step 486 withthe next activity. If at step 488 the new rule is not in the same familyas this rule, the new rule is updated to satisfy and update the new rulewith the Activity. The sub-process may end at step 494.

The optimizer 245 is an application and tool which works in conjunctionwith the rules engine 240 and a location based plan (e.g., a route fortrucking), to provide individual associated with mobile units 105 a-105c an interactive tool to plan their day including, e.g., when and whereto take breaks. The optimizer 245 provides the individual associatedwith a mobile unit 105 a-105 c optimal overlap of breaks to satisfy asmany regulations and policy's as possible to maximize theirproductivity, while still being compliant with policies and regulationsfor all geographic regions the individual associate with mobile units105 a-105 c plans to be in.

By way of example, a driver intends to drive from Utah to California.The driver must follow the Federal Motor Carrier Safety Administration(FMCSA) Hours of Service rules the Nevada workday break rules andCalifornia workday break rules. The optimizer 235 is configured tooverlay all of the rules and identify that by taking two 10 minutebreaks and one 30 minute break may satisfy all rules in thesejurisdictions. Moreover, the optimizer 245 is configured to furtherrecognize that the 30 minute break needs to occur between the hours of afirst time (X) and a second time (Y) to be compliant. This informationpermits the driver to better plan the trip, and determine when and whereto take required breaks.

The optimizer 245 may accept a number of inputs to create the optimizedplan including:

-   -   An origin and destination.        -   Example: The driver knows they need to travel from            Milwaukee, Wis. to New York, N.Y. They enter the origin,            destination and start time as inputs. The optimizer 245            works with a routing software 260 to determine the route for            the driver, and then may display best options for breaks            that align with rules & regulations for the locales the user            intends to be traveling through.    -   A multi-stop route.        -   Example: Not all trips are direct. The driver knows that the            intended travel from Milwaukee, Wis. to New York, N.Y., will            have a stop in Buffalo, N.Y. The origin, destination and            start time may be entered. Stops may be added with an order            and indication about how long each stop may take. The            optimizer 245 may employ a routing software to determine the            route for the driver, and then display best options for            breaks that align with rules and regulations for the            jurisdictions that the user anticipates traveling through.            The system 100 may automatically compensate for entering new            time zones, e.g., for adjusting total times.    -   A route in a standardized format including stops and times for        segments as well as times stopped from another application by        way of an API.

The optimizer 245 may take into account all rules currently applied toan individual associate with mobile units 105 a-105 c as well as any newrules that may be applied during the route because of entering newregions.

-   -   Example: As a driver who needs to follow FMCSA Hours of Service,        when selecting a route going to Oakland Calif., the rules may        take into account where the driver is currently located, a        14-hour shift, an 11-hour drive time, and when a 30-minute break        must be taken (or if already taken). Any new rules may be taken        into account that apply because the driver will be entering the        California region.

As part of the optimizer 245, or as a separate route optimizer tool, afunction is provided that identifies all rules that should be followedfor a given route. Moreover, the optimizer 245 may be configured toidentify an activity that satisfies more than one rule and may recommendthat activity as a better option. Optimizer 245 may be configured toidentify if the route plus activities required to satisfy necessarycompliance rules may go past the individual associated with a mobileunit 105 a-105 c expected end of day (rule). In this case, an optimizedset of rules may be returned, with a message or recommendationsuggesting a different end point be created, and to re-optimize. Thisre-optimization may change the individual's rules due to any newgeography. This functionality may be accessed directly by a custom userinterface tailored for this capability which may accept a startlocation, an end location, and any points between. This routeoptimization functionality may also be accessed by another applicationlike a trip planner that may provide another layer of detail into theindividual's activities.

FIG. 5 is a flow chart of an example process for route optimization, theprocess performed according to principles of the disclosure. The entrypoint to the process begins at 500, which may be a callable functionaccepting the following as input parameters: current user, such as anindividual associated with a mobile unit 105 a-105 c, a start locationand a time including any anticipated stop or stops with location andestimated duration, and an end location. At step 505, the start, stopand end locations may be provided to a routing tool 260. At step 510,the routing tool 260 determines at least one route. At step 515, therouting tool 260 provides a set of latitude, longitude and time asresults that represent the determined route. The route typically isrepresented by a large set of latitude, longitude, date/time. Thesepoints represent every predestined distance, e.g., 5 miles, but isconfigurable, of the route.

At step 520, a first latitude and longitude set is identified to be usedby the Rules Engine 240 to initiate building a planned route. At step525, the rules engine is called to update rules for the period 400 forthe input parameters. At step 530, a check is made to determine if thereare more points of latitude and longitude, and if so, the rule engine iscalled again at step 525 with the next latitude and longitude set tocontinue updating rules for the period 400. The update rules for periodmarks any existing and new rule as satisfied if they are satisfied by acurrent activity. If there are no further points of latitude andlongitude, then at step 535, all rules for the current period that arenot marked satisfied are located. At step 540, the first or nextunsatisfied rule is obtained. At step 545, a check is made to see ifthere is more than one rule of the same type for an overlapping period.If not, then processing continues at step 565. If there is more than onerule of the same type for the overlapping period, then at step 550, anevaluation is done to determine if a family relationship preventsoverlap. At step 555, for overlapping rules, a check is made todetermine if any share a family. If not, processing continues at step560. If so, a check is made at step 570 to determine if all rules are inthe same family. If yes, the processing continues at step 565.Otherwise, if the rules are not all in the same family, then at step575, those rules with the best overlap, i.e., longest duration overlap,are identified. At step 560, using the latest start time and locationand earliest end time and location of the rules, create arecommendation. At step 565, the recommendation for the rules may besaved as a result. Processing continues with step 580 where a check ismade to determine if there are more rules to be processed. If so, thenprocessing continues at step 540, otherwise, at step 585, a check ismade to determine whether or not the added at least one activityconflicts with the end of day rule. If not, the result may be returnedat step 595. The determination at step 585 may be accomplished by takingthe date and time of the last point from step 525 and adding in theduration of the at least one activity to satisfy the rule. If the resultoccurs later than the end of day rule, raise an error indicating thatthe end of route is not feasible with current route. At step 590, theend point change recommended with re-optimization message is created asa result. At step 595, the result is returned. If there isn't an issue,just return the result to the user. The process may end or return atstep 597.

Optimizer Example

A driver of a vehicle 112 a-112 c needs to drive from Las Vegas, Nev. toMountain Pass, Calif. He had driven for 7.5 hours before this new loadwas assigned to finish his day. The driver just completed his 36 hourre-start before he started this day. He plans to leave at noon as thatis when he should complete hooking up to the trailer. Referring to steps505 to 515, to illustrate an example result from a routing tool, a usermay enter:

Start Location: Dean Martin Dr, Las Vegas, Nev.

Start Date Time: 5/1/2016 12:00

<No Stops>

End Location: Clark Mt. Road, Mountain Pass, Calif.

TABLE 1 shows a result expected from the routing tool.

TABLE 1 Latitude Longitude Date Time 1 36.0672239 −115.1891994 5/1/201612:00 2 36.0110969 −115.2019974 5/1/2016 12:07 3 35.9221474 −115.22771615/1/2016 12:13 4 35.8677653 −115.3300632 5/1/2016 12:19 5 35.7471878−115.4426557 5/1/2016 12:25 6 35.7471878 −115.4426557 5/1/2016 12:31 735.7200864 −115.4323792 5/1/2016 12:37 8 35.6367557 −115.51342185/1/2016 12:43 9 35.6367557 −115.5134218 5/1/2016 12:49 10 35.4407923−115.5639171 5/1/2016 12:55 11 35.4407923 −115.5639171 5/1/2016 13:01 1235.4786224 −115.5426342 5/1/2016 13:07Referring to steps 520, 400, 530, to illustrate Update Rules for Periodbased on the route in the previous step.Rules before a First Call is shown in TABLE 2:

TABLE 2 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 8 hr Workday No May 1, 2016 May 1, 2016 HOS 480 workday04:30 12:30 no break 70 hr in Workday No May 1, 2016 May 9, 2016 HOS4200 8 days 04:30  4:30

Using the results from TABLE 1, calling Rules for Period in the RulesEngine 240 for each row shows that Call 1-Call 5 results in no changebecause the driver did not change regions, so no new rules for time,shown in TABLE 3.

TABLE 3 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 8 hr Workday No May 1, 2016 May 1, 2016 HOS 480 workday04:30 12:30 no break 70 hr in Workday No May 1, 2016 May 9, 2016 HOS4200 8 days 04:30  4:30

But for Call 6: the driver is working more than 8 hours (since he hasalready worked 7.5 hours). So now, add the 14-hour workday with breakrule.

-   -   This rule has the parent of 8-hour workday so it supersedes the        8-hour rule. 8-hours will be removed (shown by strikethrough)        and 14-hours will be added as shown in TABLE 4 in the third row.    -   This rule requires the driver take a 30 min break. So that rule        gets added too, as shown in the last row of TABLE 4.

TABLE 4 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value

70 hr in 8 days Workday No May 1, 2016 May 9, 2016 HOS 4200 04:30  4:3014 hr workday with Workday No May 1, 2016 May 1, 2016 HOS 840 break04:30 18:30 30 min Hours of Break No May 1, 2016 May 1, 2016 HOS 30Service Break 07:30 15:30

Calls 7 and 8 result in no change because the driver did not changeregions; therefore no new rules for time, as shown in TABLE 5.

TABLE 5 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 70 hr in Workday No May 1, 2016 May 9, 2016 HOS 4200 8days 04:30  4:30 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break 30 min Break No May 1, 2016 May 1, 2016HOS 30 Hours of 07:30 15:30 Service Break

However, for Call 9, the route just added the California region bycrossing the state line. Therefore, California break rules now need tobe added, as shown in the last three rows of TABLE 6.

TABLE 6 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 70 hr in Workday No May 1, 2016 May 9, 2016 HOS 4200 8days 04:30  4:30 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break 30 min Break No May 1, 2016 May 1, 2016HOS 30 Hours of 07:30 15:30 Service Break 10 min Break No May 1, 2016May 1, 2016 CA 10 Break 1 06:30 14:30 Breaks 10 min Break No May 1, 2016May 1, 2016 CA 10 Break 2 10:30 18:00 Breaks 30 min Break No May 1, 2016May 1, 2016 CA 30 Lunch 08:30 12:30 Breaks Break

Calls 10-12 result in nochange because the driver did not changeregions; therefore no new rules for time, as shown in TABLE 7.

TABLE 7 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 70 hr in Workday No May 1, 2016 May 9, 2016 HOS 4200 8days 04:30  4:30 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break 30 min Break No May 1, 2016 May 1, 2016HOS 30 Hours of 07:30 15:30 Service Break 10 min Break No May 1, 2016May 1, 2016 CA 10 Break 1 06:30 14:30 Breaks 10 min Break No May 1, 2016May 1, 2016 CA 10 Break 2 10:30 18:00 Breaks 30 min Break No May 1, 2016May 1, 2016 CA 30 Lunch 08:30 12:30 Breaks Break

To illustrate an overlap example (steps 535-580), using TABLE 7 as afinal ruleset for optimization, the first rule and second rule are usedto begin as shown in TABLE 8.

TABLE 8 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 70 hr in Workday No May 1, 2016 May 9, 2016 HOS 4200 8days 04:30  4:30 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break

Since these rules are of the same type (Workday) and they cover the sameperiod, they are evaluated together. Moreover, these rules are in thesame family (HOS). Both rules are in the same family, so they can'toverlap. Therefore, the 14 hour workday with break may be put back onthe primary table. Add to that the recommendation (step 565) that thedriver has 61 hours and 3 minutes left to work in 8 days or before a36-hour restart. Notice the 70 hours in 8 days (see TABLE 8) is gone, asshown in TABLE 9.

TABLE 9 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break 30 min Break No May 1, 2016 May 1, 201630 Hours of 07:30 15:30 Service Break 10 min Break No May 1, 2016 May 1,2016 CA 10 Break 1 06:30 14:30 Breaks 10 min Break No May 1, 2016 May 1,2016 CA 10 Break 2 10:30 18:00 Breaks 30 min Break No May 1, 2016 May 1,2016 CA 30 Lunch 08:30 12:30 Breaks Break

To review for Overlap, we would start with the next rule shown in TABLE10.

TABLE 10 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 14 hr Workday No May 1, 2016 May 1, 2016 HOS 840workday 04:30 18:30 with break

There is no overlap as this is the only Workday rule. A recommendation(step 565) may be added that the driver ends the workday at 18:30. Bothof the Workday rules are now complete so they are no longer on thetable, as shown in TABLE 11.

TABLE 11 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 30 min Break No May 1, 2016 May 1, 2016 30 Hours of07:30 15:30 Service Break 10 min Break No May 1, 2016 May 1, 2016 CA 10Break 1 06:30 14:30 Breaks 10 min Break No May 1, 2016 May 1, 2016 CA 10Break 2 10:30 18:00 Breaks 30 min Break No May 1, 2016 May 1, 2016 CA 30Lunch 08:30 12:30 Breaks Break

To review for overlap (step 545), begin with the first rule and movingforward, referring to TABLE 11. Since these break rules are of the sametype (Break) and they cover the same period they are evaluated together.Some of the rules are in the same Family (CA Breaks) (step 555). Sincenot all rules are in the same family, identify which rules from thefamily fit best. This may be done using the duration (step 575). Becauseboth the “30 min Hours of Service Break” and the “30 min Lunch Break”are 30 minutes, the tool recommends overlapping these (step 560).Overlap rules may find rules with the highest minutes of overlap in acase where it is not as clear cut as being the same. A recommendationmay be added that the driver take a 30 min break between now and 12:30(step 565).

Both of the 30 minute breaks were taken care of last pass so they are nolonger on the table, as shown in TABLE 12.

TABLE 12 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 10 min Break No May 1, 2016 May 1, 2016 CA 10 Break 106:30 14:30 Breaks 10 min Break No May 1, 2016 May 1, 2016 CA 10 Break 210:30 18:00 Breaks

To review again for Overlap, begin with the first two rules, as shown inTABLE 12. These rules are of the same type (Break) and they cover thesame period so they may be evaluated together. The rules are in the sameFamily (CA Breaks) (step 555). Both rules are in the same family, sothey can't overlap (step 570). Add a recommendation that the driver hasto take a 10 min break between now and 14:30 (step 565).

Since both of the 30 minute breaks were taken care of last pass they areno longer on the table, as shown in TABLE 13.

TABLE 13 Rule Valid Valid Rule Rule Type Satisfied Period Start PeriodEnd Family Value 10 min Break No May 1, 2016 May 1, 2016 CA 10 Break 210:30 18:00 Breaks

To review Overlap (step 545), we would start with the next rule, asshown in TABLE 13.

There is no overlap as this is the last rule on the table. Add arecommendation that the driver has to take a 10 min break between nowand 18:00.

Based on the above example, the driver could receive five messages:

-   -   You have 61 hours and 3 min left to work in 8 days or before a        required 36-hour restart.    -   Your workday must end before 18:30.    -   You need to take a 30 min break between now and 12:30.    -   You need to take a 10 min break between now and 14:30.    -   You need to take a 10 min break between now and 18:00.

The compliance module 252 is an application that works with the rulesengine 240 to ensure a user associated with a mobile unit 105 a-105 c isin compliance with the rules that must be followed based on theirgeographic position (current and historic). To enable the user to becompliant, the compliance module 252 is configured to provideinformation about upcoming rules to follow. The compliance module 252may be configured to provide the user a warning or alert based on aconfigured time period that they may soon be out of compliance.

-   -   Example: workday must end in the next 30 min or will be out of        compliance with company policy on overtime.

The compliance module 252 may be configured to notify the end user andhave the ability to notify a third party that the user is operating outof compliance.

-   -   Example: FMCSA regulation states that a driver must take a 30        min break before starting the 7^(th) hour of driving. When the        user enters their 7^(th) hour, the application will notify them        that they are now out of compliance. The driver's leader may        receive a notification (e.g., a text, an email, or the like)        letting them know that the driver is operating out of        compliance.

The compliance module 252 may configure standardized reports for theuser to review. For the transportation industry these reports may havespecific formatted reports that meet FMCSA ELD Regulations.

-   -   Example: A driver will be able to view their FMCSA Log        activities for a week in the 5-line log format.

Moreover, a web application may be provided for users to create a customreport to show a user's compliance. Reports also can be created acrossmultiple users.

-   -   Example: the leader can pull up a report of all times they were        out of compliance in the last 6 months during our semi-annual        performance review.    -   Example: a compliance officer may pull up a report of all users        who were not in compliance this week to share with individual        leaders to ensure they take corrective action.

The compliance engine uses Update Rules for Period 400 to leverage therules engine 240. Based on an application configuration, every X mile(s)(default may be 1 mile, but is configurable) the rules builder may readthe latitude (Lat), longitude (Long) from the mobile unit 105 a-105 cGPS 113 a-l13 c. The rules builder may send the Lat, Long to the rulesengine 240. The rules engine 240 may determine if there are any changesto a user associated with a mobile device 105 a-105 c rules for period.

FIG. 6A is a flow diagram showing an example of a compliance engineprocess to maintain the rules that must be complied to, the processperformed according to principles of the disclosure. At step 600, byconfiguration 266 and a programmable timer or clock function 265 is usedto initiate how often the compliance module 252 should check thelocation of a mobile unit 105 a-105 c. By default, the system 100 maymake this call every 30 seconds. The compliance module 252 interactswith the GPS 113 a-113 c on the mobile unit 105 a-105 c. Using the lastGPS position, and the obtained current position (step 605), calculatedistance traveled (step 610). A configurable setting may be used toconfigure how often the compliance module 252 should check the locationof the mobile unit 105 a-105 c. Because this typically requires a callto the server 115, the more often it runs the more data may be used. Bydefault, the system 100 may make this call every 1 mile, but isconfigurable. A step 615, a check may be made to determine if thedistance from step 610 is greater than the configured distance. If thedetermined distance is less than the configured distance, exit thefunction at step 618. Otherwise, at step 620, update rules for periodusing the rules engine 240 using current user, Lat and Long from step605. This may return any new rules for the period found based on the newgeographic position. At step 625, any new rules are saved to the rulesfor period database 206.

FIG. 6B is a flow diagram showing an example process for rule monitoringand notification, the process performed according to principles of thedisclosure. The process of FIG. 6B may be considered a sub-system forrule monitoring and notification. The sub-system rules monitor andnotification of FIG. 6B may leverage the rules for period table of therules database 206 to determine what rules a user associated with mobileunit 105 a-105 c must comply. For rules types that directly impact theuser's work, the sub-system rules monitor and notification sub-systemmay provide feedback to the user through the interface 114 a-114 c. Insome cases, the sub-system of FIG. 6B may send notifications to someoneother than the end user to alert them of an issue.

By configuration 266, rule monitoring and notification sub-systemprovides an ability to configure (step 640) how often to validatecompliance and provide feedback to the user. By default, the system 100may make this call every 5 seconds, but is configurable. At step 645, aquery for the Rules for Period table may be made. The query only returnsrules that have not yet been satisfied by a user activity (as indicatedon the rules for period table) and the valid period has started. Thequery also only focuses on the rule types that a user would neednotifications. At step 650, a sort first by type, then by valid periodend may be performed. This allows a correct order of processing therules. At step 655, a loop is created to process all rules. If thecurrent timestamp (data & time) is later than the valid period end dataand time, proceed to step 675 where an alert may be created to the userindicating that the event is overdue. Moreover, if the rule has backoffice communication set to true, at step 680 a message may be sent tothe backend server to indicate the user is out of compliance. The servermay then notify the interested parties in the manner they indicate(e.g., email, SMS, chat bot, workflow alert, or the like). At step 670,a countdown clock may be initiated or updated at the user interface oftime until out of compliance.

If at step 655 the period is not past due, then at step 660 a check ismade whether or not the rule is within a warning period. If not, thencontinue at step 670. If the rule is within a warning period, then atstep 665 an alert may be created to warn the user that an activity mustoccur soon. This alert can include audio and visual information tonotify the user that they are not in compliance with the rule. Becauseof different work configurations (safety could be an issue with somealert types if the user is driving), the notification type isconfigurable by rule. Using the notification Type Table, an audio file(if one exists) may be played located at the path indicated. The textmay be displayed in the notification, and the image may be displayed onthe screen, e.g., 114 a-114 c if an image path is provided. Processingmay continue at step 670.

An Activity is the actual record of “What has occurred” over a period oftime. And activity may have a start time, end time, start location andend location. Activities may reflect Work Performed (Driving, stuck inTraffic, Loading, Unloading, Waiting, Paperwork, etc) and other itemsthat need to be recorded for regulatory purposes (Workday, Lunch Breaks,Rest Breaks, 36-hour Restart, Sleeper, Off Duty).

-   -   Activities reflect a start and end time.        -   All activities have a duration that they occurred. To            determine this duration, the activities may be stamped with            a start and end time.    -   Activities reflect a start and end location Lat and Long to        reflect where the activities occurred.        -   All activities may have a location indicating where they            occurred. To determine this the activity may be stamped with            a Lat and Long. As some activities occur at a given            location, the start and end location may be the same.    -   Activities can be hierarchal in their structure.        -   Example: in the trucking industry, a driver must be in a            specific hours of service state (e.g., driving, off duty, on            duty, sleeping, personal conveyance), these activities could            be parents to activities such as loading, unloading or            stuck-in-traffic if further detail is needed. The            stuck-in-traffic could resolve the need to determine if a            driver is earning at least minimum wage every hour if they            are paid by the mile.    -   Activities can be added/configured.        -   If a company using the system 100 needs to track a new            activity in accordance to a rule or as an event for            compensation or billing, these can be added using the            activity logger.    -   Activates can be associated to rules. An activity may be        associated to more than one rule, and more than one rule may be        associated to an activity.        -   Example: a company could create a break activity; and may            associate that activity to the break rule. This could be            taken further to create a lunch break activity that could be            associated to only some breaks.    -   Activities may be used to show compliance to rules.        -   Example: in the trucking industry the set of activities            (driving, off duty, on duty, sleeping, personal conveyance)            would be created to satisfy FCMSA Hours of Service Logging            rules. By recording the time spent in each of these            activities, a driver's compliance to these regulations may            be demonstrated.    -   Activities can be used to pay for work performed.        -   Example: An organization could write extracts of activities            and push them to a compensation calculation tool to            determine a portion or all of an individual's pay. As an            example, if a company needed to pay a driver for time spent            in traffic without moving, they could create a            “stuck-in-traffic” activity, then extract it and provide it            to the compensation calculation tool to pay the driver for            that time.    -   Activities can be used to invoice for work performed.        -   Example: an organization could write extracts of activities            and push them to a billing tool to determine a portion or            all of the charges for a customer. As an example if an HVAC            specialist spends 2.5 hours cleaning ducts, this recorded            activity can be sent to a billing system to generate the            labor portion of a customer's invoice.    -   Specific user inputs of activities/events can be configured.        These actions/events may be used to show compliance.        -   Example: a user may input the start of a workday by pressing            a “clock in” button.    -   A user may be notified of an expected input based on a rule        configuration.        -   Example: 30 min after a user indicates that they are going            to take their 30 min break, the user may be prompted to            record the time they come off of break.    -   A portal may allow an individual with proper security to update        activities.        -   Example: an individual left for the day 3 hours ago, and            forgot to clock out. The individual called and asked that            their manager clock them out at the correct time. This may            be permitted based on rule configurations.    -   Activities that are configured to allow edits can be further        configured to have an edit approval process.        -   Example: a manager updates an individual's time record to            reflect the time they left the office at the individual's            request, however policy requires the individual to            acknowledge that change.

An Event is the actual record of something that happened. A keydifference between activities and events is that an event is a specifictime, where and activity provides a time and duration. Events aretriggered by something external to the system like the connection to thetruck. For Example: (Start Driving, Stop Driving, Engine On).

-   -   Events may be created on its own based on key factors.        -   Example: in the trucking example, a rule could be created to            create a start driving event when the vehicle starts moving.    -   Events may have an Event Type which is a reference object that        contains information to define events and their behavior.    -   Events are primarily used to provide a way for external factors        to assist in managing activities.        -   Recording when a truck has started moving based on            information found on a controller area network (CAN) bus            within the truck, and not the internal GPS. An interface            with the truck and the CAN bus may be provided to determine            when the truck is moving based on, e.g., the power-take-off            (PTO), speedometer, or odometer. These events may be used by            the activities application.    -   An end user may update their activities to reflect actual        events. This ability may be configured by rule to ensure        compliance with policies and regulations.        -   Example: a user took a break 4 hours ago and forgot to log            it, they may need to update their activities to indicate the            break was taken.        -   Example: a driver does not agree with the system's 100            recording driving activity, and wants to update the record            to reflect driving starting 30 min later, however the rule            has been configured to not allow an end user to update this            event to prevent log falsification.

An Activity Type is reference object that contains information to defineactivities and their behavior.

The activity type configurator 250 is a tool that may allow a user tocreate, update and remove activity types. Users may tie activities tothe rules that they satisfy. The activities can also be configured toautomatically be created based on time, location or event, or based onthe same factors, a prompt to the user to log then may be issued. Theactivities configurator 250 may leverage external tools to create theuser interface for prompts. As the back office works to create theconfigurations, the configurations may be synced on a periodic basis tothe end user's devices 110 a-110 c. The period of this integration canbe set by the back office though configuration.

FIG. 7 is an example interface to describe an activity type configuratorfunctionality, configured according to principles of the disclosure. Theactivity type configurator may include:

-   -   700—Edit/Delete Activity Type Screen may be used to search for        activity types. The user can select an activity to edit or        delete. The layout of this screen should include any data about        the activity that the user may want to have.    -   705—Search Field(s) & Search Button, Create the ability for a        user to search for activities. Name or parent are the most        likely search fields, by joining activity type to rules, a        search on activities associated to specific rules can be        performed.    -   710—An edit feature. Clicking Edit may bring up the activity        detail in a screen that allows the user to edit the activity        type record.    -   715—A delete feature. Clicking Delete removes the record from        the database    -   725—A cancel feature. Clicking Cancel may take the user back to        the main screen.    -   730—The “New Activity Type” Screen shows the key information        needed to make activities work.    -   735—The “Activity Type Name” is the name of the activity type.        Note that this may be the name of all instances (activities)        that a user creates. The name is what is displayed to users, so        it should be named appropriately. Duplicates should be avoided        when creating names as this may create confusion for users.    -   740—“Parent Activity Type” is an activity that this activity        inherits the rules it will satisfy from. If this activity will        not satisfy all rules that the parent will, don't use Parent.        Parent may often be left blank <None>.    -   745—“User Can Edit” is a flag that indicates that an end user        can make changes to activities of this type after the fact.    -   750—“Office Can Edit” is a flag that indicates that a back        office user (example: manager) can edit activities of this type.    -   755—“User Days Edit Available” is the number of days after the        activity is created that the end user may be able to edit        activities of this type.    -   760—“Office Days Edit Available” is the number of days after the        activity is created that a back office user (example: manager)        may be able to edit activities of this type.    -   765—“User Approval Required” is a flag that indicates that an        end user must review and approve any changes made by a back        office user.    -   770—“Office Approval Required” is a flag that indicates that a        back office user must review and approve any changes made by an        end user.    -   775—“Connected Rules” indicates all rules that the activity may        satisfy. If activities are created for a reason other than        rules, like to record work that was done, they should not be        tied to a rule. An example of how this would be used is if an        activity named “Break” is created, it may be attached to the        Hours of Service 30 minute break rule, California 10 minute        Break rule and California lunch break rule. All activities of        this type could then be used to satisfy those rules provided        they are for the correct duration.    -   777—When the user clicks the “Save” button, either a new        activity is created, or update an existing activity, depending        on how the user came to the page.    -   779—The next set of information may be created for each Activity        Type, Rule combination. When all are processed, the application        may return to the main page.    -   781—An activity prompt is a feature that can permits the        configuration of an end user prompt, or the automated creation        of and. By adding prompts to an activity, it works with the        overall activity configurator and displays a popup covering most        of the screen.    -   783—“Prompt Time Before Required (minutes)” is the number of        minutes before an activity is due to be done that the        application creates a popup to the user or auto generates an        activity.    -   785—“Prompt Location Radius (miles)” is the radius of a circle        around a specific geocode (latitude/longitude) that when that        radius is crossed, a popup to the user may be created or auto        generates an activity    -   787—“Prompt Event Trigger” is a list of triggers that can be        used to trigger, a popup to the user may be created or auto        generates an activity. For the trucking industry, the connection        to the truck is leveraged to bring in events such as, e.g.,        wheels in motion.    -   789—“Auto Create Activity” is a flag that, if yes, indicates        that when the time, location or event occurs, an activity is        auto created for the user.    -   791—“Cut and Paste Prompt Code Here” is a text box in which the        user may paste all code for a popup. This may be injected into        the main page when the event occurs. This feature permits        tailoring to the end user's experience.    -   793—Any HTML/Javascript tool can be used to create the code so        long as it permits the user to cut and paste it into the text        box of 791.    -   795—Save the current record.    -   797—Skip this record. No prompts are needed for this        rule/activity type combo.

The activity logger 220 and editor 215 encompasses the tools whichcreate activities, including start and finish times in which to measurecompliance against. As these activities are configured to show breakstaken as well as specific work performed, they can also be used to feedcompensation and billing systems to ensure accurate pay or invoicing forwork.

The Activity Logger 220 is a tool that may be used by a user associatedwith a mobile unit 105 a-105 c to log activities. The activity logger220 is primarily an API (Application Program Interface) that may beaccessed by prompts. FIG. 8A is an illustration of functional blockdiagram of an activity logger, configured according to principles.

In FIG. 8A, the functions include:

-   -   821—Create Activity (see FIG. 8B for example flow diagram)        -   a. This provides the ability to create an activity. This            method may be used to create activities that are already            complete.        -   b. If the log the activity is being created for does not            permit overlap, this method prevents the user from creating            overlapping activities.        -   c. As the activity is now created, Call Set Rules to            Satisfied    -   816—Start Activity (see FIG. 8C for example flow diagram)        -   a. This may create an incomplete activity and mark the            Current flag to True. Only one activity per Log can have            current flag set to True. If Start Activity is called and            there is a current activity, the application may return an            error that may be handled by the UI. Most common may be a            question “Do you want to complete your previous activity?”            However, based on the activity, each situation can be            scripted by the developer of the UI to provide the best user            experience.        -   b. If the log the activity is being created for does not            permit overlap, this method may throw an error that a future            activity has been recorded and must be changed before this            activity can be started.        -   c. This method may Create an activity using the current            information. It may require a Log and activity type to be            passed in.        -   d. It may set Start Time to the current timestamp        -   e. It may set the Start Lat and Long to the current GPS            location (provided the GPS is providing an accurate            position. Otherwise, it may wait for an accurate location or            request one from the user)    -   817—End Activity (see FIG. 8D for an example flow diagram)        -   a. This method may complete the current activity by setting            the End time to current and End Lat and Long to the current            GPS location (provided the GPS is providing an accurate            position. Otherwise, it may wait for an accurate location or            request one from the user).        -   b. It may set the current flag to False        -   c. As the activity is now created, Call Set Rules to            Satisfied    -   826—Search Activity (see FIG. 8E for an example flow diagram)        -   a. This is a method that may find all Activities that match            a set of parameters provided by the user. The result may be            returned as complete Activity Objects.        -   b. Search Activity may also be callable as a web service            from other applications. This is expected to be used to pass            activities that are compensable and/or billable activities            as a part of the users work process to external systems.    -   831—Update Activity (see FIG. 8F for an example flow diagram)        -   a. This method may update the activity        -   b. If the log the activity is being created for does not            permit overlap, this method may prevent the user from            creating overlapping activities.        -   c. After the update, Call Remove Satisfied and Set Rules to            Satisfied.    -   832—Delete Activity (see FIG. 8G for an example flow diagram)        -   a. This method may Delete the activity        -   b. Call Remove Satisfied    -   840—Set Rules to Satisfied (Activity) (see FIG. 8H for an        example flow diagram)        -   a. This method may find and update all rules that are            satisfied by a new or updated activity.    -   845—Remove Satisfied (Activity) (see FIG. 8I for an example flow        diagram)        -   a. This rule may identify any rules that need to have the            satisfied flag removed. After the flag is removed, on an            update, the application may attempt to rematch rules.    -   850—Manage Approvals (see FIG. 8J for an example flow diagram)        -   a. Identify who needs to be notified        -   b. Notify the correct users based on their desired method            -   i. Email            -   ii. SMS            -   iii. Activity Popup Prompt (see Activity Configurator                #24) [May create event]            -   iv. Web Client Application (Your notifications) [See                Activity Editor]    -   805—Get Event (see FIG. 8K for an example flow diagram)        -   a. Get event is a function that leverages the event            functionality. It is a query to the Event Table to identify            if a specific event occurred.    -   836—Approve Activity (List of Activities) (see FIG. 8L for an        example flow diagram)        -   a. This may allow a user to approve one or more activities.            It may accept a list of activities to provide the developers            of interfaces the ability to have an “Approve All” feature.    -   837—Disapprove Activity (List of Activities) (see FIG. 8M for an        example flow diagram)        -   a. This may allow a user to disapprove one or more            activities. It may accept a list of activities to provide            the developers of interfaces the ability to have an “Approve            All” feature.    -   800—Location Prompt Helper (Lat, Long, Radius) (see FIG. 8N for        an example flow diagram)        -   a. This simple function takes a Target Lat, Long and mile            radius as parameters.        -   b. It then leverages the GPS to determine current Lat, Long.        -   c. It may return one if the current location is in the            radius        -   d. It may return zero if the current location is outside the            radius        -   e. It may return nine if the GPS accuracy is poor    -   838—Get GeoCode (Location Name) (see FIG. 8O for an example flow        diagram)        -   a. This function may return Null if the service is down. It            may make a call to a Geocoding service (Example: Google            Maps)        -   b. If the function is available, the application may return            the Geo Code for the location found, or a request for more            information if more than one location is found.

FIG. 8B is a flow diagram showing an example process for a createactivity, performed according to principles of the disclosure, startingat step 850. This flow corresponds to the create activity function 821shown in FIG. 8A. At step 855, a check is made to determine if a userhas permission to create an activity. If the user does not havepermission, then at step 875, an error code may be returned. If the userdoes have permission, then at step 860 a check is made to determine ifthe log permits overlap. If so, then the process continues at step 880.If not, then at step 865, a query may be made for existing activitieswith an overlapping start and end date. At step 870, a check may be madeto determine if there are any conflicts found. If there are conflicts,an error code may be returned. Otherwise, if no conflicts are found,then at step 880 an activity may be created. At step 840, the rule orrules may be set to satisfied. At step 850, a check is made to determineif the activity requires approval. If not, then the process completes atstep 897. If the activity requires approval, then at step 875 approvalsare managed and obtained. At step 897, the process may end.

FIG. 8C is a flow diagram showing an example process for a startactivity, performed according to principles of the disclosure, startingat step 900. This flow corresponds to the start activity function 816shown in FIG. 8A. At step 902, a check may be made to determine if theuser has permission to create activity. If not, then an error code maybe returned at step 912. If the user does have permission, then at step904, a check may be made to see if there is current activity in the log.If not, then at step 905 a return error code of “Only 1 Current ActivityAllowed” indicating there is already a current activity in the log maybe set and the process may complete at step 930. However, if there is nocurrent activity at step 904, then at step 906 a check may be made todetermine if the log allows overlap. If so, then processing continues atstep 914. If overlap is not permitted, then at step 908 a query may bemade for existing activities with overlapping start and end times. Atstep 910, a check may be made to determine if any conflicts are found.If yes, then return an error code at step 912. If, however, there are noconflicts found at step 910, then at step 914 a check may be made todetermine if a location was provided with this request. If not, then atstep 918 a current location of the mobile units 105 a-105 c may bedetermined using GPS 113 a-113 c. Processing may continue at step 920.If at step 914, a current location was passed into this function, thenat step 916, the current time may be acquired from a clock 265. At step920, a check may be made to determine if the GPS data is accurate. Ifthe GPS data is deemed not accurate, one or more attempts to acquireaccurate GPS data may be attempted at step 924. If the GPS data isdeemed accurate then processing continues at step 922, otherwise if theGPS data is deemed not accurate an error code may be set at step 228 andthe process may complete at step 930. If the GPS data is deemed accurateat step 922, then an activity may be created with current location andtime. The process may complete at step 930.

FIG. 8D is a flow diagram showing an example process for an endactivity, performed according to principles of the disclosure, startingat step 932. This flow corresponds to the end activity function 817shown in FIG. 8A. At step 934 a check is made to determine if a user haspermissions to create an activity. If not, then an error code may bereturned at step 946. If the user has permissions, then at step 936 acheck may be made if there is a current activity in the log. If not,then at step 938 a no current activity error code may be returned.However, if there is a current activity at step 936, then at step 940 acheck may be made to determine if the log allows overlap. If so, thenprocessing continues at step 948. If overlap is not permitted, then atstep 942 a query may be made for existing activities with overlappingstarting and end times. At step 944, a check may be made to determine ifany conflicts are found. If yes, then return an error code at step 946.If, however, there are no conflicts found at step 944, then at step 948a check may be made to determine if a location was provided with thisrequest. If not, then at step 952 a current location of the mobile units105 a-105 c may be determined using GPS 113 a-113 c. Processing maycontinue at step 956. If at step 948, a current location was passed intothis function, then at step 950, the current time may be acquired from aclock 265. At step 954, a check may be made to determine if the GPS datais accurate. If the GPS data is deemed not to be accurate, one or moreattempts to acquire accurate GPS data may be attempted at step 956. Ifthe GPS data is deemed accurate at step 958, then processing continuesat step 962; otherwise, if the GPS data is deemed not to be accurate atstep 958, an error code may be set at step 960 and the process maycomplete at step 968. If the GPS data is deemed accurate at step 962,then an activity may be created with current location and time. Therules may be set to satisfied at step 840. The process may complete atstep 930.

FIG. 8E is a flow diagram showing an example process for a searchactivity, performed according to principles of the disclosure, startingat step 1270. This flow corresponds to the search activity function 826shown in FIG. 8A. At step 1272 using criteria provided, locate allactivities that match. At step 1274, for each log activity, a check ismade to determine if the user has permission to view the log. If not,then no activity is added to the result. If the user does havepermission, then at step 1278, the activity or activities may be addedto the result. At step 1282, a check is made to determine if there aremore activities in the search result. If there are, processing continuesat step 1276. If not, the process completes at step 284 returning theresult.

FIG. 8F is a flow diagram showing an example process for an updateactivity, performed according to principles of the disclosure, startingat step 1300. This flow corresponds to the update activity function 831shown in FIG. 8A. At step 1302 a check may be made to determine if theuser has permission to update activity. If not, then an error may bereturned at step 1310. If the user has permission, then at step 1304 acheck may be made to determine if the log allows overlap. If not, thenat step 1306 a query for existing activities may be made withoverlapping start and end points. At step 1308, a check may be made todetermine if any conflicts are found. If there are any conflicts, thenat step 1310 an error result may be returned. If, however, there are noconflicts at step 1308, then processing continues at step 1314. If atstep 1304, the log allows overlap, then at step 1314 a check may be madeto determine if the update requires approval. If not, then at step 1322the activity may be updated, and processing continues at step 1324. Ifat step 1314, the update requires approval, then at step 1316, a newactivity may be created with information for the update. At step 1318,update existing activity with a new ID in pending approval field. Atstep 850, the approval is managed. At step 845 satisfied may be removedfor the activity. At step 840, the rules may be set to satisfied. Atstep 1312 the process may complete.

FIG. 8G is a flow diagram showing an example process for a deleteactivity, performed according to principles of the disclosure, startingat step 1330. This flow corresponds to the delete activity function 832shown in FIG. 8A. At step 1332 a check is made to determine if the userhas permission to update activity. If not, then an error may be returnedat step 1344. If the user has permission, then at step 1334 a check maybe made to determine if the delete requires approval. If not, then atstep 1340 the activity may be deleted. If, however, approval isrequired, then at step 1336 update to the existing activity is marked bya “0” indicating pending approval for deletion. At step 850 the approvalfor deletion is managed. At step 845, the removal may be satisfied, theactivity effectively deleted. The process ends at step 1346.

FIG. 8H is a flow diagram showing an example process for set rules tosatisfied, performed according to principles of the disclosure, startingat step 1350. This flow corresponds to the set rules to satisfiedfunction 840 shown in FIG. 8A. Every time an activity is created orupdated, this function may be called. The remove satisfied function(FIG. 8I) should be called before this set rules to satisfied functionfor every update. At step 1352, all rules that apply are obtained. Thismay include a query for rules for period where a valid start is beforeactivity start: a valid end is after activity start and through join,the rules should be associated to this activity type. Rules should notalready be marked satisfied. At step 1354 a check may be made todetermine whether or not any rules were found. If not, then at optionalstep 1360 there is nothing to do and the process returns at step 1370.If there is at least one rule found, then at step 1356 a check is madeto determine if more than one rule was found. If no, then at step 1358for the rule found set satisfied flag to yes. The process completes atstep 370. If at step 1356, more than one rule was found, then at step1362 a check may be made to determine if any of the rules are in thesame family. If not, then at step 1364 the satisfied flag may be set toyes for all rules found, and the process completes at step 1370. If atstep 1362 there are rules in the same family, then at step 1366 thesatisfied flag may be set for all rules not in the same family. At step1368, for each family set found, locate the rule with the longestduration in the respective family and set the satisfied flag to yes. Theprocess ends at step 1370.

FIG. 8I is a flow diagram showing an example process for removesatisfied, performed according to principles of the disclosure startingat step 1372. This flow corresponds to the remove satisfied function 845shown in FIG. 8A. Every time an activity is created or updated, thisfunction may be called. At step 1374, all rules with the Activity may beobtained which may include querying for rules with that Activity fromthe rules for period. At step 1376 a check may be made to determine ifthe activity was deleted. If yes, then at step 1378 satisfied may be setto no and update Activity on all rules to null. At step 1380, allactivities that could satisfy the rule are obtained. At step 1382, acheck may be made to determine if any activities were found. If not,processing continues at step 1394. If an activity was found, then atstep 1382 all rules having the Activity may be extracted. At step 1386,a check may be made to determine whether or not the extracted rule is inthe same family as this rule. If yes, then at step 1388 a check is madeto determine if there are more activities. If yes then processingcontinues at step 1384, if not, then processing continues at step 1394.If at step 1386, the rule is not in the same family as this rule, thenat step 1390 the rule is updated to satisfied and Activity may beupdated. Processing continues at step 1394.

If at step 1376 the activity was determined not to be deleted, then atstep 1377 for each rule, compare the rule with the updated activity. Atstep 1392, a check may be made to determine if the activity stillsatisfies the rule. If not, the processing continues at step 1378.However, if the activity still satisfies the rule, then at step 1394 acheck may be made to determine if all rules have been evaluated. If not,then processing continues at step 1377 with the next rule. If all ruleshave been evaluated, then at step 1396, the process may end.

FIG. 8J is a flow diagram showing an example process for manage approvalperformed according to principles of the disclosure, starting at step1400. This flow corresponds to the manage approvals function 850 shownin FIG. 8A. At step 1402 obtain users selected preferred notificationmode, for sending notifications to the user's device 110 a, or userinterface 114 a. At step 404, a check is made to determine whether ornot the user wants a pop-up prompt. If yes, then at step 1406 an eventmay be created with type “approval required.” At step 1420 the processend. If no at step 1404, then at step 1410 a check is made to determineif the user wants email notification. If yes, then at step 1412 an emailmay be prepared and sent such as via, e.g., simple mail transportprotocol (SMTP), and processing continues at step 1414. If no at step1416, then at step 1418 may want web notification, the notification maybe saved in the web notifications table at step 1414 for eventualdisplay to the user on, e.g., user interface 114 a. Alternatively, ifthe user elected for no notifications, the process ends at step 1420

FIG. 8K is a flow diagram showing an example process for get eventperformed according to principles of the disclosure, starting at step1416. This flow corresponds to the get event function 805 shown in FIG.8A. At step 1418 the events database 225 may be queried to retrieveevents that have not yet been reported. Reported acts is a control toensure that events are only reported one time, preventing duplicateactivities or prompts being provided to the user. At step 1420 a checkis made to determine if an event has been found with the event type. Ifyes, then set reported to true for events and return event(s). At step1426 the process ends.

FIG. 8L is a flow diagram showing an example process for approveactivity performed according to principles of the disclosure, startingat step 1428. As an action may be approved or disapproved by a user at alater time, the state of the activity for approval could be stored withan “Approval ID”. The Approval ID could indicate 3 possible states. Ifthe Approval ID is 0, the user is approving a delete, if the Approval IDis the same as the Activity ID, then the user is approving a create,lastly if the Approval ID is the ID of another activity, this is anupdate. This flow corresponds to the approve activity function 836 shownin FIG. 8A. At step 1430, for all activities provided as parameters, atstep 1432 a check is made to determine if the user has permission toapprove the activity. If not, at step 1446 an error is returned and theprocess completes at step 1448. If the user does have permission, thenat step 1434 a check may be made to determine whether the Approval ID iszero. If yes, then at step 1442, the activity may be deleted and theprocess continues at step 1444. If, however, the Approval ID is notzero, then at step 1436 a check may be made to determine whether or notthe Approval ID is the same as the Activity ID. If the Approval ID isnot the same as the Activity ID, then the activity with the ID equal tothe pending Approval ID may be deleted. Processing continues at step1440. Otherwise, if the approval_ID is the same as the Activity ID, thenat step 1440 the pending Approval ID is removed. At step 1448 theprocess ends.

FIG. 8M is a flow diagram showing an example process for disapproveactivity performed according to principles of the disclosure, startingat step 1450. As an action may be approved or disapproved by a user at alater time, the state of the activity for approval could be stored withan “Approval ID”. The Approval ID could indicate 3 possible states. Ifthe Approval ID is 0, the user is approving a delete, if the Approval IDis the same as the Activity ID, then the user is approving a create,lastly if the Approval ID is the ID of another activity, this is anupdate. This flow corresponds to the Disapprove activity function 837shown in FIG. 8A. At step 452, control is established to process allactivities provided. At step 1454 a check may be made to determinewhether or not the user has permission to approve an activity. If not,an error may be returned at step 1462. If the user has permission, thenat step 1456 a check may be made to determine whether or not theApproval ID is zero. If not 0, then the activity should be deleted as itrepresents an unapproved create or updated activity, processingcontinues at step 1464. If the Approval ID is zero, then the pendingApproval ID is removed to reflect the unapproved delete of the activity.At step 1464 a check may be made to see if there are more activities. Ifso, then processing continues at step 1454 for the next activity. Ifnot, then processing ends at step 1466.

FIG. 8N is a flow diagram showing an example process for a locationprompt helper performed according to principles of the disclosurestarting at step 1468. The location prompt may be used to compare theposition of a mobile unit 105 a-105 c and another location. The processwould determine if the mobile unit is within a specific configureddistance, which could be done using the Haversine formula or othergeographic distance formula to determine if a point falls within aradius of another point. This flow corresponds to the location prompthelper function 800 shown in FIG. 8A. At step 1470, the current locationof the mobile unit 105 a-105 c may be obtained using GPS 113 a-113 c. Acheck may be made at step 1472 to determine if the GPS data is accurate.If not accurate, then at step 1474 retries may be attempted to acquireaccurate GPS data. If the GPS data is deemed accurate at step 1472 orstep 1476, then at step 1480 the Haversine formula may be used todetermine if the GPS point falls inside the radius of a given location.If not, then at step 1486 false may be returned. If within radius, atrue may be returned, the process ends at step 1486.

FIG. 8O is a flow diagram showing an example process for a get geocodeperformed according to principles of the disclosure, starting at step1488. This flow corresponds to the get geocode function 838 shown inFIG. 8A. At step 1490, a check may be made to determine whether or not anetwork link 130 is available. If not, an error is returned at step 1492and processing ends at step 1499. If a network link 130 is available,then a GIS service may be called at step 1494 providing a name of alocation, e.g., an address, a city, a county or a zip code. At step1496, a check may be made to determine if a single point geocode wasreturned. If not, an error may be returned indicating more informationrequired. The process may end at step 1499.

FIG. 9 is a functional block diagram of an event API 232 to provide anexample of how an activity such as Drive Time Start Event could beprocessed to manage an activity. This Figure shows how a vehicle 112 acould interact with a mobile device 135 including a set of methods topermit an external system 1600 to interact with an activity engine 1611of Mobile Device 135, configured according to principles of thedisclosure. The external system 1600 may be a separate platform for atransportation company or other entity for which logging, tracking andservices provided by system 100 is desired, or may be a Vehicle 112a-112 c. In this example, a vehicle 112 a-112 c which may be equippedwith onboard monitoring electronics 1602 which may include a CAN busthat may sense and provide real-time information related to the statusand state of the vehicle 112 a-112 c that may sense the PTO engaged witha speedometer indicating a speed greater than zero and the odometer maybe changing. This information or the like may be communicated to therespective computing device 110 a-110 c. At step 1605 the on-boardmonitoring electronics has detected that the vehicle has switched to adrive state. The onboard control logic, may be interpreted by abroadband router 121 or other device, which could then call “publishevent” with a “drive time start” event at step 1610 using event API 232which creates a “drive time start event” at step 1615 for entry intoevent table 225. An event listener 1620 may query the event table 225for an event on a predetermined schedule, such as, e. g., every 1, 5 or10 secs, or other configurable time period. Once the event listener 1620discovers an event, the methods in the Activity Engine 1561 may becalled to find out what to do with the event. At step 1625, a check maybe made to determine if an event occurred. If not, the event listener1620 continues to query for an event. If an event has occurred, at step1630 a search for prompt for the event type may be initiated using aprompt user table 1514. At step 1635, a check may be made to determineif a prompt was found for the event type. If not, the event listener1620 continues to query for an event. If found, at step 1640 the promptfor start driving may be retrieved from the prompt user action table1514. A check may be made to determine if this is an auto createactivity at step 1645. If yes, then at step 1650 a check may be made todetermine if this is a start of event. If yes, then call activity startfunction 816, which updates the activity table 235. If not a start ofevent then call activity end 817, which updates the activity table 235.If at step 1645 it was determined that this is not an auto createactivity, then at step 1654 a screen pop-up may be created for the userinterface. At step 1658, the action (created in 791) from the prompttable may be used to create the pop-up content, which may be returned tothe computing device 110 a-110 c. The process may continue as the eventlistener continues to scan the event table 225 for a new event.

In the example of FIG. 9 , the event API 232 may create a new Event withthe following example information (note the Event Type should alreadyexist). TABLE 14 illustrates an event type table. TABLE 15 illustratesan event table.

TABLE 14 Event Type Table Event Type ID Name 543 Drive Time Start

TABLE 15 Event Table Event Activity Event Event ID Type ID Event Time IDReported 101 543 8/22/2016 14:06:00 <null> False

In Table 15, Event ID is a system generated number. Event Type ID may belooked up based on the name provided to create. Event Time is a timestamp. If the time is provided by the calling application, that time isused. If none is provided, the timestamp is the current time. ActivityID may be populated after an activity is created. Event Reported is setto false to indicate to the event listener 1620 that this event has notyet been found.

When the activity engine 1611 finds an event, it sets Event Reported toTrue, this is shown below in TABLE 16.

TABLE 16 Event Table Event Activity Event Event ID Type ID Event Time IDReported 101 543 8/22/2016 14:06:00 <null> True

The Activity Engine 1611 may search the prompt user action table 1514for an Event Type. TABLE 17 illustrates an example of the prompt useraction table 1514. An example of a record is shown below. The ActivityName is Driving. Auto create is true.

TABLE 17 Prompt User Action Prompt Prompt Event Auto Time Location TypeCreate Is Start Activity Rule Id Action Minutes Miles ID Activity EventType ID 947 <null> <null> <null> 543 True True 9 Activity Type User UserOffice Office User Office Log Activity Parent Act'ty Can Edit Can EditApprov Approv. Type Type Id ID Name Edit Davs Edit Days Req'd Req'd Id 2<null> Driving True 90 True 365 True False 33

Events can start or end an activity. In this example this is a startevent so it may be used to create an activity. This is accomplished bycalling Activity Create 816 in the Activity Logger API. An activity maybe created that looks like that looks like TABLE 18.

TABLE 18 Activity Table Activity Log Activity End User ID ID Type IDStart Time Time Created Version 325 888 2 Aug. 22, 2016 <null> False 114:06:00 Pending End Approval Approved Start Lat Start Long End Lat LongCurrent ID True 40.7484405 −73.9856644 <null> <null> True <null>In TABLE 18:

-   -   i. Activity ID may be a random number    -   ii. Log ID may be the user's log that matches the Log Type in        the Activity Log Type (33)    -   iii. Activity Type ID is the ID of the type of activity that is        being created. In this example that is 2 (Driving) as seen in        the Activity Type table above.    -   iv. Start Time: the timestamp is used on the event shown above.    -   v. End Time: As this activity is not completed, just being        started the end time is null. Note, this is not a valid activity        until this ends.    -   vi. User Created: This was created by the system not the user or        by the back office.    -   vii. Version: The activity may show version 1 to indicate that        it has not been changed.    -   viii. Approved: drivers not expected to approve automated        action.    -   ix. Start Lat & Long: These are the Lat & Long of the position        at time Start Activity was called.    -   x. End Lat & Long: These are null as we have not ended the        activity yet.    -   xi. Current: As this is the Current Activity (can only have 1 at        a time per log), set it to True.    -   xii. Pending Approval: The activity doesn't need to be approved        so this is set to <null>.

The system 100 may also record driver data including identification dataand authentication data. In this way a historical record of the drivermay be maintained. The record may include which mobile units were drivenby the driver, geographic route, date, times and duration of driveractivity. The record may comprise an aggregated historical record toconsolidate a driver's history over multiple mobile units. Driveractivity may be maintained in a central database and may be collectedvia satellite or wireless communication link. A driver's recordedhistorical activities may also be employed to compute billing, pay, andtaxes.

This system provides a geographic regulatory compliance toolset tomanage a mobile workforce. By leveraging the power of a GlobalPositioning System and a Geographic Information System, our toolprovides a powerful geographic business rules engine to use real-timelocation tracking to determine specific regulations and policies that amobile user must comply with. The system combines expected user tasks,route, optimized break plan and user input to develop an organized planthat will be managed though a common view, that clearly depicts allactivities expected of the user. Workday plans are fluid and can beupdated by end users or back office to ensure clear communication ofexpectations.

The system and methods according to principles of this disclosure mayinclude compliance management processes to increase organizationalcompliance to regulations and policies, which may include notificationsto a user of upcoming actions required to improve personnel compliancewith jurisdictional regulations and company policies. Multiplenotification methods may be provided, including methods that provide asafe experience for a driver. The system and methods according toprinciples of this disclosure may notify a user and others of real-timecompliance issues in order that the situation may be managed, rectified,or dealt with as they occur or before they occur.

The optimizer according to principles of this disclosure maximizesworkforce productivity by recommending, e.g., optimal time blocks totake a breaks based on the driver current previous, current and futurelocations and the regulations and associated policies. The optimizerintegrates a work plan to provide a singular experience for a user tomanage and track their day

The system according to principles of this disclosure includes standardinputs to create events and activities. To reduce the need for end userdata entry, events provide a way to assist or automate activitycreation. Standard event processing for geo-position is provided using aGPS device to provide the ability to create an event based on the user'scurrent physical location. Another standard event generator mayoriginate from a vehicle connection with key event interpretation andmanagement. The system may also include a standard method to connect toexternal inputs for expanded capability.

In one aspect, according to principles of this disclosure, an activitymanagement system may provide a centralized record of activities for amultiplicity of users, and related regulations to maintain regulatorycompliance verification. The activity management system may simplifycompensation and maximize billing processes by using individuals'activities extracted from the centralized records, such as a database.

In one aspect, the system and methods according to principles of thisdisclosure system may provide maximum flexibility by providing a simpleconfiguration process for rules, activities and events. Configurationsmay be sent to end user devices without requiring software updates orinstalls to simplify and expedite the process of rolling out.

Activity Types, Event Types and Rules can be created, updated anddeleted on a server, and passed to one or more mobile units. Uponreceiving these changes, the end user application at the one or moremobile units can enforce new rules, permit new activity types andautomate or prompt new actions, based on events. The operation of theapplication at the mobile unit may be dynamically modified by thesechanges, providing a dynamic nature of its configuration, while keepingfoundational abilities as described herein.

The system configured according to principles of the disclosure mayemploy several transactional elements that may be dynamically used tocreate and monitor rules, activities, and events to provide a record ofwhat was required, and what was done. Beyond recording, the systemconfigured according to principles of the disclosure may use thisinformation to provide feedback to a user to enable the user to improveperformance. To do this, rules that need to be complied with may bedynamically identified from the set of configured rules, based on auser's role, and location. These rules may be assigned a time period inwhich the rules need to be enforced based on when the user entered thatlocation. The system configured according to principles of thedisclosure may also include events, which are moments in time thatsomething occurred; these events may be trigged by, e.g., time,location, server communication, or a vehicle. The events may be used tocreate activities, and as the activates are created, activities areapplied to the rule set to which a user must comply, to show complianceas it occurs.

While the disclosure has been described in terms of exemplaryembodiments, those skilled in the art will recognize that the disclosurecan be practiced with modifications in the spirit and scope of theappended claims. These examples are merely illustrative and are notmeant to be an exhaustive list of all possible designs, embodiments,applications or modifications of the disclosure.

What is claimed:
 1. A system comprising: a memory havingcomputer-readable instructions stored thereon; and a processor thatexecutes the computer-readable instructions to: receive a start locationand an end location of a mobile unit; determine a route from the startlocation to the end location, the route comprising a plurality of setpoints between the start location and the end location; compile a set ofrules for a user of the mobile device to comply with along the route by:identifying a rule that applies to the user at each of the plurality ofset points, wherein the rule is based at least on a location determinedfrom the plurality of set points; and adding the rule to the set ofrules upon determining that the rule does not already exist in the setof rules; and add a set of recommendations to a work plan for the userto follow based upon the set of rules.
 2. The system of claim 1, whereineach of the plurality of set points comprises a latitude and longitudecoordinate.
 3. The system of claim 1, wherein each consecutive set pointof the plurality of set points is separated by a predetermined distancealong the route.
 4. The system of claim 1, wherein the processor furtherexecutes the computer-readable instructions to: receive a start date andstart time at the start location; and associate a set point date and setpoint time with each of the plurality of set points, wherein the setpoint date and the set point time are computed based upon the start dateand the start time, and wherein the rule at each of the plurality of setpoints is further identified based upon the set point date and the setpoint time at each of the plurality of set points.
 5. The system ofclaim 1, wherein to compile the set of rules, the processor furtherexecutes the computer-readable instructions to: determine an existingset of rules that apply to the user at the start location; and updatethe existing set of rules based upon the rule identified at each of theplurality of set points to obtain the set of rules.
 6. The system ofclaim 1, wherein the rule is further based upon a total number of hoursthe user has worked by a start of each of the plurality of set points,and wherein at each of the plurality of set points, upon determiningthat the total number of hours is greater than a threshold, theprocessor further executes the computer-readable instructions to:determine that a new rule supersedes an existing rule on the set ofrules; delete the existing rule from the set of rules; and add the newrule to the set of rules.
 7. The system of claim 1, wherein theprocessor further executes the computer-readable instructions to:determine that a first set point of the plurality of set points is in anew geographic region compared to a second set point of the plurality ofset points; identify another rule that applies to the new geographicregion; and add the another rule to the set of rules.
 8. The system ofclaim 1, wherein the processor further executes the computer-readableinstructions to optimize the set of rules based upon a rule type by:determining that a first rule and a second rule from the set of ruleshave a same rule type; selecting the first rule to remain on the set ofrules based upon determining that the first rule encompasses the secondrule; and deleting the second rule from the set of rules.
 9. The systemof claim 8, wherein selecting the first rule to remain on the set ofrules and deleting the second rule from the set of rules comprisesdetermining that the first rule and the second rule belong to a samerule family.
 10. The system of claim 8, wherein the processor furtherexecutes the computer-readable instructions to update the set ofrecommendations based upon optimizing the set of rules.
 11. The systemof claim 1, wherein the set of recommendations comprises at least one ofa number of hours left to work for the user on the route, a workday endtime for the user, a number of breaks that need to be taken by the userduring the workday, a time duration for each of the number of breaks, abreak end time by when each of the number of breaks needs to be taken.12. The system of claim 1, wherein the processor further executes thecomputer-readable instructions to monitor compliance of the set of rulesbased upon data received from the user.
 13. A method comprising;receiving, by a processor, a start location and an end location of amobile unit; determining, by the processor, a route from the startlocation to the end location, the route comprising a plurality of setpoints between the start location and the end location; compiling, bythe processor, a set of rules for a user of the mobile device to complywith along the route by: identifying a rule that applies to the user ateach of the plurality of set points, wherein the rule is based at leaston a location determined from the plurality of set points; and addingthe rule to the set of rules upon determining that the rule does notalready exist in the set of rules; and adding, by the processor, a setof recommendations to a work plan for the user to follow based upon theset of rules.
 14. The method of claim 13, wherein the rule is furtherbased upon a total number of hours the user has worked by a start ofeach of the plurality of set points, and wherein, at each of theplurality of set points, upon determining that the total number of hoursis greater than a threshold, the method further comprises: determining,by the processor, that a new rule supersedes an existing rule on the setof rules; deleting, by the processor, the existing rule from the set ofrules; and adding, by the processor, the new rule to the set of rules.15. The method of claim 13, further comprising: determining, by theprocessor, that a first set point of the plurality of set points is in anew geographic region compared to a second set point of the plurality ofset points; identifying, by the processor, another rule that applies tothe new geographic region; and adding, by the processor, the anotherrule to the set of rules.
 16. The method of claim 13, furthercomprising: optimizing, by the processor, the set of rules based upon arule type by: determining that a first rule and a second rule from theset of rules have a same rule type; selecting the first rule to remainon the set of rules based upon determining that the first ruleencompasses the second rule; and deleting the second rule from the setof rules.
 17. The method of claim 16, further comprising updating theset of recommendations based upon optimizing the set of rules.
 18. Anon-transitory computer-readable media comprising computer-readableinstructions stored thereon that when executed by a processor cause theprocessor to: receive a start location and an end location of a mobileunit; determine a route from the start location to the end location, theroute comprising a plurality of set points between the start locationand the end location; compile a set of rules for a user of the mobiledevice to comply with along the route by: identifying a rule thatapplies to the user at each of the plurality of set points, wherein therule is based at least on a location determined from the plurality ofset points; and adding the rule to the set of rules upon determiningthat the rule does not already exist in the set of rules; and add a setof recommendations to a work plan for the user to follow based upon theset of rules.
 19. The non-transitory computer-readable media of claim18, wherein each of the plurality of set points comprises a latitude andlongitude coordinate.
 20. The non-transitory computer-readable media ofclaim 19, wherein each consecutive set point of the plurality of setpoints is separated by a predetermined distance along the route.